Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0429395dd81f5520e08cb7bab5a5ca912f96a4f6ad3812139fa9cfee8ef85f47

Tx prefix hash: 0087d73379283abcacda5715406968974368c86f3114e9aa9e0dc71f76c59bf7
Tx public key: 4fe9e0825c406833f78225dfbd475599d77dc63f4b0522b38cd02403f19c534f
Timestamp: 1719887798 Timestamp [UCT]: 2024-07-02 02:36:38 Age [y:d:h:m:s]: 00:317:20:12:00
Block: 1056622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227125 RingCT/type: yes/0
Extra: 014fe9e0825c406833f78225dfbd475599d77dc63f4b0522b38cd02403f19c534f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b773bea3dcafda6207a19a938c51eab625ebd7b8d967119e37eb7496c6aa2ea 0.600000000000 1527039 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": 1056632, "vin": [ { "gen": { "height": 1056622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b773bea3dcafda6207a19a938c51eab625ebd7b8d967119e37eb7496c6aa2ea" } } ], "extra": [ 1, 79, 233, 224, 130, 92, 64, 104, 51, 247, 130, 37, 223, 189, 71, 85, 153, 215, 125, 198, 63, 75, 5, 34, 179, 140, 208, 36, 3, 241, 156, 83, 79, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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