Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cadc819121bdaf2fd39f2bfe8f93c25769b8044bdd9573c550ae43b1b5db1d1

Tx prefix hash: f767d92a3c66775b53b0a118b3d7995345b4617117a8c243a5a44160e08ef037
Tx public key: 97b73dadf2366e814fa1ca1f80a851b3acf87ed45157c693d1d74a27246f8257
Timestamp: 1649272490 Timestamp [UCT]: 2022-04-06 19:14:50 Age [y:d:h:m:s]: 02:342:20:22:27
Block: 474608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764609 RingCT/type: yes/0
Extra: 0197b73dadf2366e814fa1ca1f80a851b3acf87ed45157c693d1d74a27246f825702110000000306faf294000000000000000000

1 output(s) for total of 16.422032964000 dcy

stealth address amount amount idx
00: a6fc64c7896ab47e74cb35bccf8c9acec9ed5c199933ffe5442e6a086d167296 16.422032964000 894683 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 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": 474618, "vin": [ { "gen": { "height": 474608 } } ], "vout": [ { "amount": 16422032964, "target": { "key": "a6fc64c7896ab47e74cb35bccf8c9acec9ed5c199933ffe5442e6a086d167296" } } ], "extra": [ 1, 151, 183, 61, 173, 242, 54, 110, 129, 79, 161, 202, 31, 128, 168, 81, 179, 172, 248, 126, 212, 81, 87, 198, 147, 209, 215, 74, 39, 36, 111, 130, 87, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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