Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0600bda314460e6dad4aaf6997f95126269bf1ad3cc546f34ca46bf31de9a32

Tx prefix hash: 175c2e1d387d1fa8edb8063481237d73c7cdf6d07dec60e0231e640066b9d9b6
Tx public key: 2e7dad265bfd3c0f839331eb953f4a2524db3037df66e098abc46288b11236f8
Timestamp: 1715030898 Timestamp [UCT]: 2024-05-06 21:28:18 Age [y:d:h:m:s]: 00:191:21:33:59
Block: 1016374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137355 RingCT/type: yes/0
Extra: 012e7dad265bfd3c0f839331eb953f4a2524db3037df66e098abc46288b11236f80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a493aa8c392b1f784e6a0873931597de7cb58893ae3a44b5c3b5dfa96d57d3 0.600000000000 1479935 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": 1016384, "vin": [ { "gen": { "height": 1016374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a493aa8c392b1f784e6a0873931597de7cb58893ae3a44b5c3b5dfa96d57d3" } } ], "extra": [ 1, 46, 125, 173, 38, 91, 253, 60, 15, 131, 147, 49, 235, 149, 63, 74, 37, 36, 219, 48, 55, 223, 102, 224, 152, 171, 196, 98, 136, 177, 18, 54, 248, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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