Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33cb03faecfc3c36fa3055166038b3d7dbbfb7716025f5cd49c20770de04df0

Tx prefix hash: a8ad94d9a14eb0e942e4331c5818b639fd2f8c165645359b52679206e4de7418
Tx public key: a23688817286167dfd6355c21e545bbb723b537afd0c5b79ea142ac61f6d4f5e
Timestamp: 1675485285 Timestamp [UCT]: 2023-02-04 04:34:45 Age [y:d:h:m:s]: 01:343:13:54:43
Block: 689390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506530 RingCT/type: yes/0
Extra: 01a23688817286167dfd6355c21e545bbb723b537afd0c5b79ea142ac61f6d4f5e021100000002272bcc39000000000000000000

1 output(s) for total of 3.189809003000 dcy

stealth address amount amount idx
00: 3e0728a54f6a37ba6038e77e2ba78416101d51d3a8a82dc5a9cc3d94708aed5c 3.189809003000 1132060 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": 689400, "vin": [ { "gen": { "height": 689390 } } ], "vout": [ { "amount": 3189809003, "target": { "key": "3e0728a54f6a37ba6038e77e2ba78416101d51d3a8a82dc5a9cc3d94708aed5c" } } ], "extra": [ 1, 162, 54, 136, 129, 114, 134, 22, 125, 253, 99, 85, 194, 30, 84, 91, 187, 114, 59, 83, 122, 253, 12, 91, 121, 234, 20, 42, 198, 31, 109, 79, 94, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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