Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1511bbac20eb4d24098681d241c640ba2f518d61a1369731f8ba01bb79cc1854

Tx prefix hash: 535ef2aa4e6244e887003bbdf527f020899148f8e3945f218753bfada3ad6f02
Tx public key: 8d0bf9c390632c7d5ae540ea1646c8d43d4c7527657f8c7ec36b5ead15636804
Timestamp: 1706567188 Timestamp [UCT]: 2024-01-29 22:26:28 Age [y:d:h:m:s]: 01:284:05:00:53
Block: 946169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461924 RingCT/type: yes/0
Extra: 018d0bf9c390632c7d5ae540ea1646c8d43d4c7527657f8c7ec36b5ead1563680402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35d8a925e07eaf48667aaee42ef9d636fecf521c7f059f2623ca2c052b287f2e 0.600000000000 1404499 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": 946179, "vin": [ { "gen": { "height": 946169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35d8a925e07eaf48667aaee42ef9d636fecf521c7f059f2623ca2c052b287f2e" } } ], "extra": [ 1, 141, 11, 249, 195, 144, 99, 44, 125, 90, 229, 64, 234, 22, 70, 200, 212, 61, 76, 117, 39, 101, 127, 140, 126, 195, 107, 94, 173, 21, 99, 104, 4, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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