Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5fc2c377771ecb164ad72d521ef80d995a9970bb62abb178ae4bf8a269afed

Tx prefix hash: 7e0bc20ac68b95cdb4dc4ed2274f5e6f1dcde9665edf7ab539e6ba904357fb76
Tx public key: 2cd3bd2eb8e20fb4aa115d069ee5aad9dd97cee7b7900fc56f1e35991071dd0c
Timestamp: 1709538905 Timestamp [UCT]: 2024-03-04 07:55:05 Age [y:d:h:m:s]: 01:045:09:58:19
Block: 970839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293464 RingCT/type: yes/0
Extra: 012cd3bd2eb8e20fb4aa115d069ee5aad9dd97cee7b7900fc56f1e35991071dd0c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a572288dd985885f8b9eac6cfdce58aed419d777e6e95e6341d6f2f05f7d1a9a 0.600000000000 1430702 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": 970849, "vin": [ { "gen": { "height": 970839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a572288dd985885f8b9eac6cfdce58aed419d777e6e95e6341d6f2f05f7d1a9a" } } ], "extra": [ 1, 44, 211, 189, 46, 184, 226, 15, 180, 170, 17, 93, 6, 158, 229, 170, 217, 221, 151, 206, 231, 183, 144, 15, 197, 111, 30, 53, 153, 16, 113, 221, 12, 2, 17, 0, 0, 0, 3, 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