Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74fc7ba6c489f9bf6cc1917fc455f38073c8d7ce438c59f1c62873bcac18d527

Tx prefix hash: efa31a2d112d9d220c1642d76f4ababc1e9c39cdb46038bbc2cc6e0b2bab618c
Tx public key: 977d535546b968af40fe3e44c499d6d55b4b872fe8a4c8abd7691f21a958becf
Timestamp: 1637586918 Timestamp [UTC]: 2021-11-22 13:15:18 Age [y:d:h:m:s]: 04:363:11:47:30
Block: 379695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1302589 RingCT/type: yes/0
Extra: 01977d535546b968af40fe3e44c499d6d55b4b872fe8a4c8abd7691f21a958becf02110000001a379224c2000000000000000000

1 output(s) for total of 0.033877646131 xmr

stealth address amount amount idx tag
00: afb0d20b5299a3abb18e7f2d09d900750417daf7499600e4e1b4721a29e91b7d 0.033877646131 767431 of 0 -

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 dinastycoin-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": 379705, "vin": [ { "gen": { "height": 379695 } } ], "vout": [ { "amount": 33877646131, "target": { "key": "afb0d20b5299a3abb18e7f2d09d900750417daf7499600e4e1b4721a29e91b7d" } } ], "extra": [ 1, 151, 125, 83, 85, 70, 185, 104, 175, 64, 254, 62, 68, 196, 153, 214, 213, 91, 75, 135, 47, 232, 164, 200, 171, 215, 105, 31, 33, 169, 88, 190, 207, 2, 17, 0, 0, 0, 26, 55, 146, 36, 194, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: