Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93014f314eaf264c6baf64a7606cb56f19f84f584d4bdda522b0574be1fdce57

Tx prefix hash: 0fb45067cc1b7c6b65def220b933ec9a0c3d58f7c5d8b5ce9300fab1322d5c45
Tx public key: ccdce73e28f0c7bbe91d05d4104876b558a7ca04e5f11d1ffb74d1d5a7f1dbea
Timestamp: 1718543972 Timestamp [UCT]: 2024-06-16 13:19:32 Age [y:d:h:m:s]: 00:275:21:06:16
Block: 1045501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197139 RingCT/type: yes/0
Extra: 01ccdce73e28f0c7bbe91d05d4104876b558a7ca04e5f11d1ffb74d1d5a7f1dbea02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e408df01b815c1e4e21ec118369525cf4026b2d4fd7df2f910715b28ec82f45 0.600000000000 1515088 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": 1045511, "vin": [ { "gen": { "height": 1045501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e408df01b815c1e4e21ec118369525cf4026b2d4fd7df2f910715b28ec82f45" } } ], "extra": [ 1, 204, 220, 231, 62, 40, 240, 199, 187, 233, 29, 5, 212, 16, 72, 118, 181, 88, 167, 202, 4, 229, 241, 29, 31, 251, 116, 209, 213, 167, 241, 219, 234, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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