Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb15631c808faef9f7765ed63fd746b65760696d0d48ff6c3778a17d60f7694d

Tx prefix hash: 2f5354f8b5d7eeee7913130bf556b2373d81677c3f6cba686788e86ddd06db75
Tx public key: ec2a3dae17f0d2dfa6f64b3c05d5dbc888a04e237bc30a0684d0384a119dcc28
Timestamp: 1722571732 Timestamp [UCT]: 2024-08-02 04:08:52 Age [y:d:h:m:s]: 00:319:15:52:49
Block: 1078872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228298 RingCT/type: yes/0
Extra: 01ec2a3dae17f0d2dfa6f64b3c05d5dbc888a04e237bc30a0684d0384a119dcc28021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 335b475c56b21e23e810910e04b5e1250ed45d75a5178ec8dc614b7320483d64 0.600000000000 1551587 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": 1078882, "vin": [ { "gen": { "height": 1078872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335b475c56b21e23e810910e04b5e1250ed45d75a5178ec8dc614b7320483d64" } } ], "extra": [ 1, 236, 42, 61, 174, 23, 240, 210, 223, 166, 246, 75, 60, 5, 213, 219, 200, 136, 160, 78, 35, 123, 195, 10, 6, 132, 208, 56, 74, 17, 157, 204, 40, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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