Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c3319ce38bad35835c1348df8d9a1008279268aec5f618258a63e9206d305d

Tx prefix hash: 91d4d23399e811532eef9259c7e5fc60555e1f1a4f6d6633fd9dcd47c28274a5
Tx public key: 96238286dc9b486a833a339db1c17ea774d2e3e9ffce217adfc1022912350769
Timestamp: 1724803073 Timestamp [UCT]: 2024-08-27 23:57:53 Age [y:d:h:m:s]: 00:252:08:27:52
Block: 1097367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180238 RingCT/type: yes/0
Extra: 0196238286dc9b486a833a339db1c17ea774d2e3e9ffce217adfc1022912350769021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af64a3f7a00cee7b5ad165ee394df4024179d1b3d10074d26b6c54c3fe0b9f3c 0.600000000000 1572762 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": 1097377, "vin": [ { "gen": { "height": 1097367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af64a3f7a00cee7b5ad165ee394df4024179d1b3d10074d26b6c54c3fe0b9f3c" } } ], "extra": [ 1, 150, 35, 130, 134, 220, 155, 72, 106, 131, 58, 51, 157, 177, 193, 126, 167, 116, 210, 227, 233, 255, 206, 33, 122, 223, 193, 2, 41, 18, 53, 7, 105, 2, 17, 0, 0, 0, 3, 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