Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9683bde70c3013d2fddb0635c57a7223082a74e2060c1607e5feb422b456a99f

Tx prefix hash: ca491ef8d8114057e5662ac8b0ae57639b02afdf858a4b9e8983f8e41c6de82f
Tx public key: 9f885ff80b29327c49012223b0a2dd190937fd87d965e62fc771b041cecb3c64
Timestamp: 1709927874 Timestamp [UCT]: 2024-03-08 19:57:54 Age [y:d:h:m:s]: 00:237:04:53:00
Block: 974058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169827 RingCT/type: yes/0
Extra: 019f885ff80b29327c49012223b0a2dd190937fd87d965e62fc771b041cecb3c6402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0cb4095ac6e6075d4ad1a47022a657e3531097c20edf49f8e3ea274d10f5a17 0.600000000000 1434003 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": 974068, "vin": [ { "gen": { "height": 974058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0cb4095ac6e6075d4ad1a47022a657e3531097c20edf49f8e3ea274d10f5a17" } } ], "extra": [ 1, 159, 136, 95, 248, 11, 41, 50, 124, 73, 1, 34, 35, 176, 162, 221, 25, 9, 55, 253, 135, 217, 101, 230, 47, 199, 113, 176, 65, 206, 203, 60, 100, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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