Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2aa59fbc20ffea0d55dd9e2cc2ce37efd6a280dc01aed6acfc635df73446a2c

Tx prefix hash: a0dde3ccf669a75afd322e05d4a2b15c1380d1b4d2e4dd98d0aea066820d379f
Tx public key: 266cf291b374b37caa0235118d3c0aed415e6f12156ea88e6517dfe671b30f4e
Timestamp: 1688399048 Timestamp [UCT]: 2023-07-03 15:44:08 Age [y:d:h:m:s]: 01:241:11:06:43
Block: 795824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433678 RingCT/type: yes/0
Extra: 01266cf291b374b37caa0235118d3c0aed415e6f12156ea88e6517dfe671b30f4e02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.416135669000 dcy

stealth address amount amount idx
00: 4419ad0fda5a863c80b51b67c1ff99e3d1eb4c90b2da92070df8ccb69682ab31 1.416135669000 1246661 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": 795834, "vin": [ { "gen": { "height": 795824 } } ], "vout": [ { "amount": 1416135669, "target": { "key": "4419ad0fda5a863c80b51b67c1ff99e3d1eb4c90b2da92070df8ccb69682ab31" } } ], "extra": [ 1, 38, 108, 242, 145, 179, 116, 179, 124, 170, 2, 53, 17, 141, 60, 10, 237, 65, 94, 111, 18, 21, 110, 168, 142, 101, 23, 223, 230, 113, 179, 15, 78, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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