Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: da813693363fa8bc794c9fa85f10d008ae3be0f0b1684534144e5b415a9c79b2

Tx prefix hash: 7759f9b55ff0b8d730f48dde08c224eab7d6d952dda2d8e2b4511ca08ca75671
Tx public key: 5a2f11dc551b9f11efe3594dd236589433b2dabd9affc12a9c9b08fc14dfee94
Timestamp: 1729421173 Timestamp [UCT]: 2024-10-20 10:46:13 Age [y:d:h:m:s]: 00:144:11:50:30
Block: 1135653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103055 RingCT/type: yes/0
Extra: 015a2f11dc551b9f11efe3594dd236589433b2dabd9affc12a9c9b08fc14dfee94021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c447cfac033a13ac9775a860ae2dc446531f066475e77b5917858d5aaf3be9 0.600000000000 1618992 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1135663, "vin": [ { "gen": { "height": 1135653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c447cfac033a13ac9775a860ae2dc446531f066475e77b5917858d5aaf3be9" } } ], "extra": [ 1, 90, 47, 17, 220, 85, 27, 159, 17, 239, 227, 89, 77, 210, 54, 88, 148, 51, 178, 218, 189, 154, 255, 193, 42, 156, 155, 8, 252, 20, 223, 238, 148, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8