Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731ee8f7080385cf3605d50d1205a80485515a416abc67e834beb73f0ce5162b

Tx prefix hash: 30283f313656ea17a31136d8eb653e6ce8fdafb6cb0e830c75c91a1bc5625e2f
Tx public key: 8d8ea8f5ee9c1c8767c91cd494b82a65c968976d3c71c3e5c3f8f1ae72ff5f94
Timestamp: 1702340005 Timestamp [UCT]: 2023-12-12 00:13:25 Age [y:d:h:m:s]: 01:138:14:54:56
Block: 911153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360224 RingCT/type: yes/0
Extra: 018d8ea8f5ee9c1c8767c91cd494b82a65c968976d3c71c3e5c3f8f1ae72ff5f9402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 658a8b94ec019436f3bfbe1e205dcdfc2fa188d5677d61edc82aad554a03e00c 0.600000000000 1368334 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": 911163, "vin": [ { "gen": { "height": 911153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "658a8b94ec019436f3bfbe1e205dcdfc2fa188d5677d61edc82aad554a03e00c" } } ], "extra": [ 1, 141, 142, 168, 245, 238, 156, 28, 135, 103, 201, 28, 212, 148, 184, 42, 101, 201, 104, 151, 109, 60, 113, 195, 229, 195, 248, 241, 174, 114, 255, 95, 148, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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