Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4741d1b93881924151466a6b51860f0c2340afaeaef4defeff9f2691ca280d0c

Tx prefix hash: 581b26b40882da695519599fc788cff04a223f0482324f6eb4eb4d43f3b1ecb4
Tx public key: 0d803eb6d769e7dae21bbfff8baa188fdaeded45cfa420f97f1ed23d061d5bd4
Timestamp: 1700858844 Timestamp [UCT]: 2023-11-24 20:47:24 Age [y:d:h:m:s]: 01:204:09:04:08
Block: 898865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407181 RingCT/type: yes/0
Extra: 010d803eb6d769e7dae21bbfff8baa188fdaeded45cfa420f97f1ed23d061d5bd40211000000014b8f5122000000000000000000

1 output(s) for total of 0.645189221000 dcy

stealth address amount amount idx
00: 71394e9bba2eefcca3440440ded3061de114d8ba70e36fb7a3449c56f2ae0d05 0.645189221000 1355302 of 0

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": 898875, "vin": [ { "gen": { "height": 898865 } } ], "vout": [ { "amount": 645189221, "target": { "key": "71394e9bba2eefcca3440440ded3061de114d8ba70e36fb7a3449c56f2ae0d05" } } ], "extra": [ 1, 13, 128, 62, 182, 215, 105, 231, 218, 226, 27, 191, 255, 139, 170, 24, 143, 218, 237, 237, 69, 207, 164, 32, 249, 127, 30, 210, 61, 6, 29, 91, 212, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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