Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9acde04f355ae440f93c801259541dd3d4c88fdde6a8e53a2ea58a876052e61a

Tx prefix hash: 46fda8c22e2eb83d1b59bcee9254402c6f0f2a5235b61500c1ed660c49d7fc5c
Tx public key: a5a12407aa3879695ec149b8f1df02a58d07a6c4d2866758d70b922bff00ff94
Timestamp: 1723675237 Timestamp [UCT]: 2024-08-14 22:40:37 Age [y:d:h:m:s]: 01:084:23:29:25
Block: 1088024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319203 RingCT/type: yes/0
Extra: 01a5a12407aa3879695ec149b8f1df02a58d07a6c4d2866758d70b922bff00ff94021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dba9bdcd131bfa5054483ddc21c5cfd0ecda14fbd04ff3e9b6c00bf0255fca41 0.600000000000 1562635 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": 1088034, "vin": [ { "gen": { "height": 1088024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dba9bdcd131bfa5054483ddc21c5cfd0ecda14fbd04ff3e9b6c00bf0255fca41" } } ], "extra": [ 1, 165, 161, 36, 7, 170, 56, 121, 105, 94, 193, 73, 184, 241, 223, 2, 165, 141, 7, 166, 196, 210, 134, 103, 88, 215, 11, 146, 43, 255, 0, 255, 148, 2, 17, 0, 0, 0, 1, 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