Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae805464e1e18fd012c6e8856b53391ed3a01986d545b3ea258ede9ab7860a5

Tx prefix hash: 8e4bc37adbde2c7877fb1fe80262dd9c84c3e4e5ef045b26cb3b31a2aa3de081
Tx public key: 8a3428ec6c5318b946e2f60e22a42ca25c83b2507d317ce7f606850771cb8d0d
Timestamp: 1722522005 Timestamp [UCT]: 2024-08-01 14:20:05 Age [y:d:h:m:s]: 00:174:09:41:38
Block: 1078466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124731 RingCT/type: yes/0
Extra: 018a3428ec6c5318b946e2f60e22a42ca25c83b2507d317ce7f606850771cb8d0d021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eb4845a2f6b76744171aff43bbc5eb2d64d3862f9c769768a8a1392be4d0488 0.600000000000 1551043 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": 1078476, "vin": [ { "gen": { "height": 1078466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eb4845a2f6b76744171aff43bbc5eb2d64d3862f9c769768a8a1392be4d0488" } } ], "extra": [ 1, 138, 52, 40, 236, 108, 83, 24, 185, 70, 226, 246, 14, 34, 164, 44, 162, 92, 131, 178, 80, 125, 49, 124, 231, 246, 6, 133, 7, 113, 203, 141, 13, 2, 17, 0, 0, 0, 19, 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