Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b9dcd3e7df1455370b4f85185d20035dcc9207a1ee4e6f8ac317165d73851ab

Tx prefix hash: d2669c9b5d1cf30791a6d8b62667cdef1826be17f47f7223b1254af68f478761
Tx public key: 46213e630c0b98f6a507277c36c3d9cb1c31a59f02ac3afd2bb70cad7f251dd6
Timestamp: 1694300903 Timestamp [UCT]: 2023-09-09 23:08:23 Age [y:d:h:m:s]: 01:167:22:08:48
Block: 844678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381080 RingCT/type: yes/0
Extra: 0146213e630c0b98f6a507277c36c3d9cb1c31a59f02ac3afd2bb70cad7f251dd602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.975508837000 dcy

stealth address amount amount idx
00: d9046373c1fc3edc35d75aac6655f37a2491391e63c7a80b95701b2bf43af7b0 0.975508837000 1298002 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": 844688, "vin": [ { "gen": { "height": 844678 } } ], "vout": [ { "amount": 975508837, "target": { "key": "d9046373c1fc3edc35d75aac6655f37a2491391e63c7a80b95701b2bf43af7b0" } } ], "extra": [ 1, 70, 33, 62, 99, 12, 11, 152, 246, 165, 7, 39, 124, 54, 195, 217, 203, 28, 49, 165, 159, 2, 172, 58, 253, 43, 183, 12, 173, 127, 37, 29, 214, 2, 17, 0, 0, 0, 2, 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