Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a5e1badf1da7fdf28f87a754602b902a7d5e6bf130a90cc5dadd284fb1e833

Tx prefix hash: 8eb95d2b0b0a048d0dd404c8510ac1ed4ddd9d47748a6ca924d956ccbb09768b
Tx public key: 913a632a16c075854b4881916309aff9d95093183c002a3b58c30aa67ca123cd
Timestamp: 1702716122 Timestamp [UCT]: 2023-12-16 08:42:02 Age [y:d:h:m:s]: 01:122:02:15:30
Block: 914264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348401 RingCT/type: yes/0
Extra: 01913a632a16c075854b4881916309aff9d95093183c002a3b58c30aa67ca123cd02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a647fceeaffc32f6fb8f54f771c8af9e20329e6e718de41b87e9538324d021 0.600000000000 1371558 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": 914274, "vin": [ { "gen": { "height": 914264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a647fceeaffc32f6fb8f54f771c8af9e20329e6e718de41b87e9538324d021" } } ], "extra": [ 1, 145, 58, 99, 42, 22, 192, 117, 133, 75, 72, 129, 145, 99, 9, 175, 249, 217, 80, 147, 24, 60, 0, 42, 59, 88, 195, 10, 166, 124, 161, 35, 205, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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