Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bb0790eeb4b41c27cebb58ca044743dfb63a1be81e9f7ce94376768fe7b9d9

Tx prefix hash: 9857e94dec9f08735422e7007cb267e502f628dd107a3b4762e8fe19a7491591
Tx public key: ab8d1024f7370b1ecfcc93b96b62614024393245fbe5322103c0dc9dbdfe503f
Timestamp: 1714249893 Timestamp [UCT]: 2024-04-27 20:31:33 Age [y:d:h:m:s]: 00:305:17:21:01
Block: 1009884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218523 RingCT/type: yes/0
Extra: 01ab8d1024f7370b1ecfcc93b96b62614024393245fbe5322103c0dc9dbdfe503f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e807109b09132f08fd8e1478549f0b463807d23ca3e305b0e069741fb0a9a3b 0.600000000000 1471680 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": 1009894, "vin": [ { "gen": { "height": 1009884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e807109b09132f08fd8e1478549f0b463807d23ca3e305b0e069741fb0a9a3b" } } ], "extra": [ 1, 171, 141, 16, 36, 247, 55, 11, 30, 207, 204, 147, 185, 107, 98, 97, 64, 36, 57, 50, 69, 251, 229, 50, 33, 3, 192, 220, 157, 189, 254, 80, 63, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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