Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ec8935058a7d2dffebb0431612e34ae6095856e454d8f6611fbe14f40230868

Tx prefix hash: e37da98311cb6b70d1dd23e23aafe2e5a1b73ab51ba7c1087b2df4f2ad8cd51d
Tx public key: 72f7629e7331a4ec5c668d9cd73f4362676195d3798a8db589760fab3cbaa4e0
Timestamp: 1723782017 Timestamp [UCT]: 2024-08-16 04:20:17 Age [y:d:h:m:s]: 00:303:03:05:55
Block: 1088907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216482 RingCT/type: yes/0
Extra: 0172f7629e7331a4ec5c668d9cd73f4362676195d3798a8db589760fab3cbaa4e0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02ecc1ae8d47bef7e8ca03f64b584da830f5563e3b36169c8dbc2a4369394af 0.600000000000 1563526 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": 1088917, "vin": [ { "gen": { "height": 1088907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02ecc1ae8d47bef7e8ca03f64b584da830f5563e3b36169c8dbc2a4369394af" } } ], "extra": [ 1, 114, 247, 98, 158, 115, 49, 164, 236, 92, 102, 141, 156, 215, 63, 67, 98, 103, 97, 149, 211, 121, 138, 141, 181, 137, 118, 15, 171, 60, 186, 164, 224, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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