Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 837a3d18a82e3cf098015e0abb13cd3d7d5df94c05cd7c38a7512b5e70d6f79a

Tx prefix hash: d8e8646fccb85eb5ae73de392defcb03dcce3501f4075b41dba9260831b2e4ea
Tx public key: 7f3c7544cea466f8f949ad71a152a0dc74aae262e746bbfe525b03bcd6961798
Timestamp: 1731918999 Timestamp [UCT]: 2024-11-18 08:36:39 Age [y:d:h:m:s]: 00:140:05:47:17
Block: 1156274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100051 RingCT/type: yes/0
Extra: 017f3c7544cea466f8f949ad71a152a0dc74aae262e746bbfe525b03bcd6961798021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de1bf3786bd17db9fedce1bf674b0dd3ff7c3cdae80bca8206e2126e8ecda344 0.600000000000 1641897 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": 1156284, "vin": [ { "gen": { "height": 1156274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de1bf3786bd17db9fedce1bf674b0dd3ff7c3cdae80bca8206e2126e8ecda344" } } ], "extra": [ 1, 127, 60, 117, 68, 206, 164, 102, 248, 249, 73, 173, 113, 161, 82, 160, 220, 116, 170, 226, 98, 231, 70, 187, 254, 82, 91, 3, 188, 214, 150, 23, 152, 2, 17, 0, 0, 0, 6, 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