Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c5b3b9005412dfc24278c340ec8f4bd09aa2aa40ca060c4d5e5f47aa00d57c

Tx prefix hash: e15127c4aa56c42a322ce5d14ec0b21717e7e8ed72b7701a71a69313128b12cd
Tx public key: 2ed3df7c03e5e72f123dc0c836c4aa2dd0aef239a191e51f1ba15751444ea1db
Timestamp: 1723249347 Timestamp [UCT]: 2024-08-10 00:22:27 Age [y:d:h:m:s]: 00:248:12:00:25
Block: 1084496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177488 RingCT/type: yes/0
Extra: 012ed3df7c03e5e72f123dc0c836c4aa2dd0aef239a191e51f1ba15751444ea1db021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19e9cf97d021d304ab4bb01c5c7dec3161d27afaca95d95b0677bc3c42cbbb2a 0.600000000000 1558793 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": 1084506, "vin": [ { "gen": { "height": 1084496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19e9cf97d021d304ab4bb01c5c7dec3161d27afaca95d95b0677bc3c42cbbb2a" } } ], "extra": [ 1, 46, 211, 223, 124, 3, 229, 231, 47, 18, 61, 192, 200, 54, 196, 170, 45, 208, 174, 242, 57, 161, 145, 229, 31, 27, 161, 87, 81, 68, 78, 161, 219, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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