Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfa49a1721fdfa0466ce90881bf174df547050338fa33e24729ff9a7945188e

Tx prefix hash: b38062f9908e67ff15342b28e835948250fb1a2d7a84b2fe292885b107c38b53
Tx public key: e0fc634212dc5738583e6e6824c6de22ee51c36de5f1b7d39a5a6c0a1780ac2b
Timestamp: 1734029456 Timestamp [UCT]: 2024-12-12 18:50:56 Age [y:d:h:m:s]: 00:099:22:59:25
Block: 1173780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71215 RingCT/type: yes/0
Extra: 01e0fc634212dc5738583e6e6824c6de22ee51c36de5f1b7d39a5a6c0a1780ac2b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e29e5f0ce4c3c34e598333e4057d37d39dd3678a9384be6f2972d00b08f9755 0.600000000000 1659841 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": 1173790, "vin": [ { "gen": { "height": 1173780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e29e5f0ce4c3c34e598333e4057d37d39dd3678a9384be6f2972d00b08f9755" } } ], "extra": [ 1, 224, 252, 99, 66, 18, 220, 87, 56, 88, 62, 110, 104, 36, 198, 222, 34, 238, 81, 195, 109, 229, 241, 183, 211, 154, 90, 108, 10, 23, 128, 172, 43, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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