Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c801e4492b18024f398c5b748372ded74fb0f78e5e8a0da2413f2ead8077aaf

Tx prefix hash: 320c9a0a82ea49328652d616154fdebd14a6177794ab43c2913db26f1159f7bc
Tx public key: f00c01780f1fb7a88c5fdedae3e493e300fa7e532e72a88deb393e265bc80a4d
Timestamp: 1737398154 Timestamp [UCT]: 2025-01-20 18:35:54 Age [y:d:h:m:s]: 00:148:17:32:39
Block: 1201601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106050 RingCT/type: yes/0
Extra: 01f00c01780f1fb7a88c5fdedae3e493e300fa7e532e72a88deb393e265bc80a4d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6e76beba1c303e54d4f991d1c9c5e7fe9955c52247674d272630648a451897 0.600000000000 1688254 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": 1201611, "vin": [ { "gen": { "height": 1201601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6e76beba1c303e54d4f991d1c9c5e7fe9955c52247674d272630648a451897" } } ], "extra": [ 1, 240, 12, 1, 120, 15, 31, 183, 168, 140, 95, 222, 218, 227, 228, 147, 227, 0, 250, 126, 83, 46, 114, 168, 141, 235, 57, 62, 38, 91, 200, 10, 77, 2, 17, 0, 0, 0, 4, 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