Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79ef5e4ac9a51aafa65b2e76d4de1a65c906e7a7248dd85eae3ae12f809e7941

Tx prefix hash: ada12e79aceeb0bdc04f642d1d996c7000b107120b188893fef25348ef117d8b
Tx public key: 96b994a3a3e801c1ff090d0c059852a891a4ef15b72e487e9e48d0cdec38cd67
Timestamp: 1702682408 Timestamp [UCT]: 2023-12-15 23:20:08 Age [y:d:h:m:s]: 01:340:09:47:18
Block: 913978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502155 RingCT/type: yes/0
Extra: 0196b994a3a3e801c1ff090d0c059852a891a4ef15b72e487e9e48d0cdec38cd67021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62fdb270bc14fe78075435b22a72418206cc93ceddb849b4eeaf23d8e57c3a9e 0.600000000000 1371258 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": 913988, "vin": [ { "gen": { "height": 913978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62fdb270bc14fe78075435b22a72418206cc93ceddb849b4eeaf23d8e57c3a9e" } } ], "extra": [ 1, 150, 185, 148, 163, 163, 232, 1, 193, 255, 9, 13, 12, 5, 152, 82, 168, 145, 164, 239, 21, 183, 46, 72, 126, 158, 72, 208, 205, 236, 56, 205, 103, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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