Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ab332f00b256b417ae74ba771ab0a7a6d5fea76ec2e36902a3726900c9dafc

Tx prefix hash: 49a70df507830de386055a6268fc1c93b1ba1b0f822a2995c1d21f4cd1534835
Tx public key: f628c0ced60b0c57657193b15ba291a68c938485440c9d86da4bb5a8d2cc1857
Timestamp: 1727061774 Timestamp [UCT]: 2024-09-23 03:22:54 Age [y:d:h:m:s]: 00:062:12:21:14
Block: 1116102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44691 RingCT/type: yes/0
Extra: 01f628c0ced60b0c57657193b15ba291a68c938485440c9d86da4bb5a8d2cc185702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f451d99ccef01cbf5d1eff3f67e9e348f087b975d62458e0accf18a9009b7f6 0.600000000000 1596469 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": 1116112, "vin": [ { "gen": { "height": 1116102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f451d99ccef01cbf5d1eff3f67e9e348f087b975d62458e0accf18a9009b7f6" } } ], "extra": [ 1, 246, 40, 192, 206, 214, 11, 12, 87, 101, 113, 147, 177, 91, 162, 145, 166, 140, 147, 132, 133, 68, 12, 157, 134, 218, 75, 181, 168, 210, 204, 24, 87, 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