Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa18e74e70ed591a65e8b6282d307d6552ab394f60751e9f11caa0c4e27061dd

Tx prefix hash: dc0f39cc11640577624f53bba02b0090a351212947ddf8b222f1f675d947b846
Tx public key: a0ec21da798d98a31fa318b129b6c26c3cbe6d7291af0f224e2c9c8eafc78344
Timestamp: 1705400904 Timestamp [UCT]: 2024-01-16 10:28:24 Age [y:d:h:m:s]: 01:321:16:30:55
Block: 936502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488766 RingCT/type: yes/0
Extra: 01a0ec21da798d98a31fa318b129b6c26c3cbe6d7291af0f224e2c9c8eafc7834402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48a4277558722e733705536556a0bca9c97bb81838d1d438a8b7148d3cdf515f 0.600000000000 1394530 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": 936512, "vin": [ { "gen": { "height": 936502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48a4277558722e733705536556a0bca9c97bb81838d1d438a8b7148d3cdf515f" } } ], "extra": [ 1, 160, 236, 33, 218, 121, 141, 152, 163, 31, 163, 24, 177, 41, 182, 194, 108, 60, 190, 109, 114, 145, 175, 15, 34, 78, 44, 156, 142, 175, 199, 131, 68, 2, 17, 0, 0, 0, 2, 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