Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334a4468832a8606e06459426bfda6c1a36344c50da402a4ec67899e5886c350

Tx prefix hash: c14e35b08b48a902f2679672003c7bedba2eaddc7c6bdc8be1bcc3822d94a290
Tx public key: cd7283aad4b63f2e59955e14b4229b01fad286c2a2f84e94194f7a0d4438aee1
Timestamp: 1720813140 Timestamp [UCT]: 2024-07-12 19:39:00 Age [y:d:h:m:s]: 00:258:09:45:40
Block: 1064304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184600 RingCT/type: yes/0
Extra: 01cd7283aad4b63f2e59955e14b4229b01fad286c2a2f84e94194f7a0d4438aee102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 810399d4719d2d3efbf6f0da8cf2c71cffcb7901ba1edef307fc6f68e37eac01 0.600000000000 1534829 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": 1064314, "vin": [ { "gen": { "height": 1064304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "810399d4719d2d3efbf6f0da8cf2c71cffcb7901ba1edef307fc6f68e37eac01" } } ], "extra": [ 1, 205, 114, 131, 170, 212, 182, 63, 46, 89, 149, 94, 20, 180, 34, 155, 1, 250, 210, 134, 194, 162, 248, 78, 148, 25, 79, 122, 13, 68, 56, 174, 225, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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