Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2730f1986e10371c4ef0f9f63e6911117f0defdd5c73247ce4ef8a1b12d936

Tx prefix hash: 2016ad652df65ec25dd65923249e0dfc4d667b7902f6b69e1d22b7ba133e496d
Tx public key: 3c9be8cae9cf3c4b84906fac001eb07947f524a7c3e686fd69c11c9b526dfe0b
Timestamp: 1705496255 Timestamp [UCT]: 2024-01-17 12:57:35 Age [y:d:h:m:s]: 01:080:04:16:28
Block: 937292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318391 RingCT/type: yes/0
Extra: 013c9be8cae9cf3c4b84906fac001eb07947f524a7c3e686fd69c11c9b526dfe0b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8de0914fdc95f1cb0ab76191bfff127856eebe6a9062de70620da65fc0ec3168 0.600000000000 1395342 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": 937302, "vin": [ { "gen": { "height": 937292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8de0914fdc95f1cb0ab76191bfff127856eebe6a9062de70620da65fc0ec3168" } } ], "extra": [ 1, 60, 155, 232, 202, 233, 207, 60, 75, 132, 144, 111, 172, 0, 30, 176, 121, 71, 245, 36, 167, 195, 230, 134, 253, 105, 193, 28, 155, 82, 109, 254, 11, 2, 17, 0, 0, 0, 2, 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