Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd150ea4d030853073b1dda90b01f12b90582098ea4da29f10d8e1780110901e

Tx prefix hash: 3b4ed056739b1d37874ba0cffffb16dcfb6112297c779819dac4f273d22e2f4c
Tx public key: ad3425a2510a4fffb956c65454a8336eb0ac8d79c47041dd0c0f210f88f068f4
Timestamp: 1721291134 Timestamp [UCT]: 2024-07-18 08:25:34 Age [y:d:h:m:s]: 00:098:05:57:16
Block: 1068271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70328 RingCT/type: yes/0
Extra: 01ad3425a2510a4fffb956c65454a8336eb0ac8d79c47041dd0c0f210f88f068f402110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fcd5df13535851719c2d572579568b349f6057634673c6140a4f4ed8210f761 0.600000000000 1539348 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": 1068281, "vin": [ { "gen": { "height": 1068271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fcd5df13535851719c2d572579568b349f6057634673c6140a4f4ed8210f761" } } ], "extra": [ 1, 173, 52, 37, 162, 81, 10, 79, 255, 185, 86, 198, 84, 84, 168, 51, 110, 176, 172, 141, 121, 196, 112, 65, 221, 12, 15, 33, 15, 136, 240, 104, 244, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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