Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8329126ff21f8b0eeb639d901c165b6d2f8d904a2530683713bda4a203fe356f

Tx prefix hash: ab04e1f732a78e9bf5a6da16bd6e3eea43c858521e1e54f7d4a50bc1126fdd6b
Tx public key: 800fd277534fb71179e33efb93ae79cba57a87b9ee46ef80971e2937d53a8e57
Timestamp: 1720953452 Timestamp [UCT]: 2024-07-14 10:37:32 Age [y:d:h:m:s]: 00:267:23:36:52
Block: 1065478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191431 RingCT/type: yes/0
Extra: 01800fd277534fb71179e33efb93ae79cba57a87b9ee46ef80971e2937d53a8e57021100000027e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06d6cff67c386b46c317528e572cdc5f329b1e54dd165b412170b7bf223b6974 0.600000000000 1536025 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": 1065488, "vin": [ { "gen": { "height": 1065478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06d6cff67c386b46c317528e572cdc5f329b1e54dd165b412170b7bf223b6974" } } ], "extra": [ 1, 128, 15, 210, 119, 83, 79, 183, 17, 121, 227, 62, 251, 147, 174, 121, 203, 165, 122, 135, 185, 238, 70, 239, 128, 151, 30, 41, 55, 213, 58, 142, 87, 2, 17, 0, 0, 0, 39, 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