Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddb386883d6a1c3605f0018d7fabcb08707ef0b1db642f621efc5513ff7c1f19

Tx prefix hash: ffd37045579df935fda205092a9e737a5612cd20dc5b1ed532dcade7160d1ac2
Tx public key: 61cea2eab87a4c5922886d54c814a96b3b82dfdf6123543197095bf1d996191e
Timestamp: 1700825924 Timestamp [UCT]: 2023-11-24 11:38:44 Age [y:d:h:m:s]: 01:347:04:15:54
Block: 898590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507004 RingCT/type: yes/0
Extra: 0161cea2eab87a4c5922886d54c814a96b3b82dfdf6123543197095bf1d996191e02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.646544308000 dcy

stealth address amount amount idx
00: 34bfd122726736cb089924c6d40fe5ed926f02cc09aa2783007b8f7c3ca2f49b 0.646544308000 1355011 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": 898600, "vin": [ { "gen": { "height": 898590 } } ], "vout": [ { "amount": 646544308, "target": { "key": "34bfd122726736cb089924c6d40fe5ed926f02cc09aa2783007b8f7c3ca2f49b" } } ], "extra": [ 1, 97, 206, 162, 234, 184, 122, 76, 89, 34, 136, 109, 84, 200, 20, 169, 107, 59, 130, 223, 223, 97, 35, 84, 49, 151, 9, 91, 241, 217, 150, 25, 30, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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