Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029b7e685df5b3bfe2fc48d2319b15a18df202203be21cdecabb212aa8970e78

Tx prefix hash: 9044cd9bcaca81fe07c2fc39e23930c38ba91e84ef305a01c3dc59edd604f141
Tx public key: b736ecc55c1f7d38aea164b0ac2d6f6be82132bdf3a66a0d37aaf764363d8b53
Timestamp: 1715726555 Timestamp [UCT]: 2024-05-14 22:42:35 Age [y:d:h:m:s]: 00:253:11:02:03
Block: 1022132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181346 RingCT/type: yes/0
Extra: 01b736ecc55c1f7d38aea164b0ac2d6f6be82132bdf3a66a0d37aaf764363d8b530211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b05c3e9efe82f95c394720d67f98c27e0f07c2e6af111ba7af5760a357702c0c 0.600000000000 1486645 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": 1022142, "vin": [ { "gen": { "height": 1022132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b05c3e9efe82f95c394720d67f98c27e0f07c2e6af111ba7af5760a357702c0c" } } ], "extra": [ 1, 183, 54, 236, 197, 92, 31, 125, 56, 174, 161, 100, 176, 172, 45, 111, 107, 232, 33, 50, 189, 243, 166, 106, 13, 55, 170, 247, 100, 54, 61, 139, 83, 2, 17, 0, 0, 0, 3, 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