Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0915f6b1a13d1230a06941716a44742d9b03da4378e8c6b7cb0c17dcd7edda1c

Tx prefix hash: 66b639e1562d2313979cc328ebfbcf728b630c2984506e5267d202f41c3a42d3
Tx public key: 2c271be56371ac7fcd4b29507453b7b8af1755ec4e258c15d566e12579934d4f
Timestamp: 1717136834 Timestamp [UCT]: 2024-05-31 06:27:14 Age [y:d:h:m:s]: 00:295:13:23:10
Block: 1033828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211222 RingCT/type: yes/0
Extra: 012c271be56371ac7fcd4b29507453b7b8af1755ec4e258c15d566e12579934d4f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f27c4e06af2037f316ea96a22aa6e16a00ad8a4fdc94172afdab0f6657624ee 0.600000000000 1502301 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": 1033838, "vin": [ { "gen": { "height": 1033828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f27c4e06af2037f316ea96a22aa6e16a00ad8a4fdc94172afdab0f6657624ee" } } ], "extra": [ 1, 44, 39, 27, 229, 99, 113, 172, 127, 205, 75, 41, 80, 116, 83, 183, 184, 175, 23, 85, 236, 78, 37, 140, 21, 213, 102, 225, 37, 121, 147, 77, 79, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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