Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae745cb168ec5ddd974f01878d60235bdf44d269a642cc97bbde912793953ca4

Tx prefix hash: ea2ef1b1a1c276456169bb47ea99598f5fbb5d1522ccd3ac066e87af48dbc7c9
Tx public key: 307e5db7654d04b7ce40e893af267429dfb6419c77f63162ce2c3d3a4f24e4ec
Timestamp: 1674087403 Timestamp [UCT]: 2023-01-19 00:16:43 Age [y:d:h:m:s]: 02:040:20:07:46
Block: 677772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550824 RingCT/type: yes/0
Extra: 01307e5db7654d04b7ce40e893af267429dfb6419c77f63162ce2c3d3a4f24e4ec02110000000152542ceb000000000000000000

1 output(s) for total of 3.485458798000 dcy

stealth address amount amount idx
00: 7f201b99d2f4e81b7ad702e73d42556473dc448f321da4b7831a73714408a27a 3.485458798000 1119567 of 0

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": 677782, "vin": [ { "gen": { "height": 677772 } } ], "vout": [ { "amount": 3485458798, "target": { "key": "7f201b99d2f4e81b7ad702e73d42556473dc448f321da4b7831a73714408a27a" } } ], "extra": [ 1, 48, 126, 93, 183, 101, 77, 4, 183, 206, 64, 232, 147, 175, 38, 116, 41, 223, 182, 65, 156, 119, 246, 49, 98, 206, 44, 61, 58, 79, 36, 228, 236, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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