Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09019bca3e34a2674a4a1c96157dc6a81a650ed74cdc0bc42f90aa7cf8fe3c6

Tx prefix hash: a9771dbf23f882550694357e92b500fb0eff82b66f5d1effd6a4273e672fc00e
Tx public key: 6f81a7e58a88f41d3b5b3c5fae5ebaba9b770a9247328c71682be40fd33daf10
Timestamp: 1724807292 Timestamp [UCT]: 2024-08-28 01:08:12 Age [y:d:h:m:s]: 00:206:00:49:30
Block: 1097405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147110 RingCT/type: yes/0
Extra: 016f81a7e58a88f41d3b5b3c5fae5ebaba9b770a9247328c71682be40fd33daf1002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05597b99591c6be106d1e1811d4b1bc3325ce6ba2b564ba7a303895bd96541f9 0.600000000000 1572800 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": 1097415, "vin": [ { "gen": { "height": 1097405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05597b99591c6be106d1e1811d4b1bc3325ce6ba2b564ba7a303895bd96541f9" } } ], "extra": [ 1, 111, 129, 167, 229, 138, 136, 244, 29, 59, 91, 60, 95, 174, 94, 186, 186, 155, 119, 10, 146, 71, 50, 140, 113, 104, 43, 228, 15, 211, 61, 175, 16, 2, 17, 0, 0, 0, 3, 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