Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc2d6d9d83a13adff567b0eda604e4e619bef924eb39581cbc42af908b893fe

Tx prefix hash: 223898640de7e495c4b04190aa5005050e911da83624fa25cfaa0f6a20cfcccb
Tx public key: 1576e1e1ce67c07933eb7bf141c40e990a66d01271e2d978f6527bd7a7bf4c8d
Timestamp: 1724299844 Timestamp [UCT]: 2024-08-22 04:10:44 Age [y:d:h:m:s]: 00:095:14:43:41
Block: 1093214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68382 RingCT/type: yes/0
Extra: 011576e1e1ce67c07933eb7bf141c40e990a66d01271e2d978f6527bd7a7bf4c8d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 533138f2698cf771f868f4a56db8a924f570ad4e7ad1595fd01811876c809a72 0.600000000000 1568111 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": 1093224, "vin": [ { "gen": { "height": 1093214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533138f2698cf771f868f4a56db8a924f570ad4e7ad1595fd01811876c809a72" } } ], "extra": [ 1, 21, 118, 225, 225, 206, 103, 192, 121, 51, 235, 123, 241, 65, 196, 14, 153, 10, 102, 208, 18, 113, 226, 217, 120, 246, 82, 123, 215, 167, 191, 76, 141, 2, 17, 0, 0, 0, 4, 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