Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24f4827414af8eac2e074a0c35009c4e4e0af9ce2e3cf08a68903eb10d50236

Tx prefix hash: 70dcfa3d7c75fe9f658fb733292f2920abc4581c8ca538b568e937faff41d6f2
Tx public key: 2d988be521c64b65a58e8cc4edad3373b9c20edc22cea7a8b857dd7c5cd1743e
Timestamp: 1578657138 Timestamp [UCT]: 2020-01-10 11:52:18 Age [y:d:h:m:s]: 04:321:16:21:34
Block: 42621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119253 RingCT/type: yes/0
Extra: 012d988be521c64b65a58e8cc4edad3373b9c20edc22cea7a8b857dd7c5cd1743e02110000000a49b77a3d000000000000000000

1 output(s) for total of 443.383755904000 dcy

stealth address amount amount idx
00: 2b9b671c0891040e0ce725ad2d3d84d9c15498e11c568254e8f2ed6a2949dd4c 443.383755904000 76853 of 0

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": 42631, "vin": [ { "gen": { "height": 42621 } } ], "vout": [ { "amount": 443383755904, "target": { "key": "2b9b671c0891040e0ce725ad2d3d84d9c15498e11c568254e8f2ed6a2949dd4c" } } ], "extra": [ 1, 45, 152, 139, 229, 33, 198, 75, 101, 165, 142, 140, 196, 237, 173, 51, 115, 185, 194, 14, 220, 34, 206, 167, 168, 184, 87, 221, 124, 92, 209, 116, 62, 2, 17, 0, 0, 0, 10, 73, 183, 122, 61, 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