Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a478f72f5a1dbb7b024dc73e3a8bf1b625b1d1392ff562283d20f1947a826ea

Tx prefix hash: 78b3e0f4fcd2cf9b48a0733dd5d89200065161119dbbc44f07eec6ae43a62759
Tx public key: 8aa8fbe83933087bab0a06dcda4d32f33d9b5f3eb2d73ee73a080fd006e95212
Timestamp: 1711901854 Timestamp [UCT]: 2024-03-31 16:17:34 Age [y:d:h:m:s]: 01:011:19:13:05
Block: 990432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269386 RingCT/type: yes/0
Extra: 018aa8fbe83933087bab0a06dcda4d32f33d9b5f3eb2d73ee73a080fd006e9521202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03e4c12a4604d447e5b6d3355eb77c165e9c3682a5653250462a976e4dc81293 0.600000000000 1450754 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": 990442, "vin": [ { "gen": { "height": 990432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03e4c12a4604d447e5b6d3355eb77c165e9c3682a5653250462a976e4dc81293" } } ], "extra": [ 1, 138, 168, 251, 232, 57, 51, 8, 123, 171, 10, 6, 220, 218, 77, 50, 243, 61, 155, 95, 62, 178, 215, 62, 231, 58, 8, 15, 208, 6, 233, 82, 18, 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