Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59cfb94df9d0fe0a99330eac15ba46fd77ff268789e6956bf6230d0ff6ca619

Tx prefix hash: 2e8a2cff040ec6e7a750b44d6723782124fadc1b9d7e5a58cf932d3923a0855f
Tx public key: b1963750d2db640080da75e8ccb8fe81551c1162039f2c5dd9e221ebcf94e9a5
Timestamp: 1745709474 Timestamp [UCT]: 2025-04-26 23:17:54 Age [y:d:h:m:s]: 00:208:17:38:21
Block: 1270185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146894 RingCT/type: yes/0
Extra: 01b1963750d2db640080da75e8ccb8fe81551c1162039f2c5dd9e221ebcf94e9a5021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb6916a4877fb64c90f6a92b054e360fd8904461f1a5f7930130a329b72a4f87 0.600000000000 1757426 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": 1270195, "vin": [ { "gen": { "height": 1270185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb6916a4877fb64c90f6a92b054e360fd8904461f1a5f7930130a329b72a4f87" } } ], "extra": [ 1, 177, 150, 55, 80, 210, 219, 100, 0, 128, 218, 117, 232, 204, 184, 254, 129, 85, 28, 17, 98, 3, 159, 44, 93, 217, 226, 33, 235, 207, 148, 233, 165, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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