Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e532917ab83db0e014c898623822b18c52ee39a8a1532710e6c0a0052c3da01

Tx prefix hash: 6154759cebe9d22c7016f30551917f84f1e387c3ea241d22650bbdb427a1bfce
Tx public key: b47d40c7a64fe7006f6dcacc4dac1df8f3d66c80d255c043bfd727ca898e1224
Timestamp: 1717267533 Timestamp [UCT]: 2024-06-01 18:45:33 Age [y:d:h:m:s]: 00:321:13:21:28
Block: 1034911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229813 RingCT/type: yes/0
Extra: 01b47d40c7a64fe7006f6dcacc4dac1df8f3d66c80d255c043bfd727ca898e122402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89db895f0de97f96fd8f91dbeeda16eeb399e19f7f32da01d587a521eda2cd4e 0.600000000000 1503430 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": 1034921, "vin": [ { "gen": { "height": 1034911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89db895f0de97f96fd8f91dbeeda16eeb399e19f7f32da01d587a521eda2cd4e" } } ], "extra": [ 1, 180, 125, 64, 199, 166, 79, 231, 0, 111, 109, 202, 204, 77, 172, 29, 248, 243, 214, 108, 128, 210, 85, 192, 67, 191, 215, 39, 202, 137, 142, 18, 36, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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