Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 828a6eed5c00d09cec7b036f3eb017be9f096dd3acfc789018fdd08281da292d

Tx prefix hash: 6ac9fb7557a4752394993931d3eca0685ddafd42c1c34cbcebcaa9e82e3b0ec2
Tx public key: ee5667ca79a80d33441c7a902ec57dfc83b0dc2c3bafdf41a097bb5876213f95
Timestamp: 1739255703 Timestamp [UCT]: 2025-02-11 06:35:03 Age [y:d:h:m:s]: 00:330:05:30:41
Block: 1216753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233853 RingCT/type: yes/0
Extra: 01ee5667ca79a80d33441c7a902ec57dfc83b0dc2c3bafdf41a097bb5876213f950211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23b839966b6cbb4d3be6993951e8043a0af7606d21c9830aa2fc808f280a053 0.600000000000 1703560 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": 1216763, "vin": [ { "gen": { "height": 1216753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23b839966b6cbb4d3be6993951e8043a0af7606d21c9830aa2fc808f280a053" } } ], "extra": [ 1, 238, 86, 103, 202, 121, 168, 13, 51, 68, 28, 122, 144, 46, 197, 125, 252, 131, 176, 220, 44, 59, 175, 223, 65, 160, 151, 187, 88, 118, 33, 63, 149, 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