Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01904c1dbad49a128a02c50597ffe1ba02c6c70b292338360dddfcb90d35f1bd

Tx prefix hash: 6033d03460845dfa71fc05f3c3020dc5b6035ce5a2c845900dfd44ca91f87b7c
Tx public key: d8eef286f68e1ed6fdf2b7722c33dfdf57f11342c1876576ea5686fe2fbb5093
Timestamp: 1630681372 Timestamp [UCT]: 2021-09-03 15:02:52 Age [y:d:h:m:s]: 04:062:15:03:34
Block: 326677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077917 RingCT/type: yes/0
Extra: 01d8eef286f68e1ed6fdf2b7722c33dfdf57f11342c1876576ea5686fe2fbb50930211000000127062e8e6000000000000000000

1 output(s) for total of 50.768165243000 dcy

stealth address amount amount idx
00: cd9f3a177aea40c6867c6ffc513e9f37b56c18fc69d6f12b83b74c9c79e4832d 50.768165243000 676784 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": 326687, "vin": [ { "gen": { "height": 326677 } } ], "vout": [ { "amount": 50768165243, "target": { "key": "cd9f3a177aea40c6867c6ffc513e9f37b56c18fc69d6f12b83b74c9c79e4832d" } } ], "extra": [ 1, 216, 238, 242, 134, 246, 142, 30, 214, 253, 242, 183, 114, 44, 51, 223, 223, 87, 241, 19, 66, 193, 135, 101, 118, 234, 86, 134, 254, 47, 187, 80, 147, 2, 17, 0, 0, 0, 18, 112, 98, 232, 230, 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