Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0b7614ca77e6ec8c13c62331bb10cf60175b844c5549f21efade97414529b2

Tx prefix hash: 6a120971c5ac1c8174a2514342d937dd910c77451200e8b0e5d50757f472b67f
Tx public key: 72e56b8dff0ba2f99e2443076ead7d45d74da7ea4d179e6bb803f449838a9d9e
Timestamp: 1706429045 Timestamp [UCT]: 2024-01-28 08:04:05 Age [y:d:h:m:s]: 01:070:16:07:40
Block: 945021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311580 RingCT/type: yes/0
Extra: 0172e56b8dff0ba2f99e2443076ead7d45d74da7ea4d179e6bb803f449838a9d9e02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e434780f2e12dc668b1ffa0e25d47b3956f6d7b11779252476bc55efec96bbe 0.600000000000 1403329 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": 945031, "vin": [ { "gen": { "height": 945021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e434780f2e12dc668b1ffa0e25d47b3956f6d7b11779252476bc55efec96bbe" } } ], "extra": [ 1, 114, 229, 107, 141, 255, 11, 162, 249, 158, 36, 67, 7, 110, 173, 125, 69, 215, 77, 167, 234, 77, 23, 158, 107, 184, 3, 244, 73, 131, 138, 157, 158, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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