Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3872610ffcde84bf4791dc2e75feb7dfc1b71e6a54b455c471e83000dc5d51ae

Tx prefix hash: 876a2956d49f791b8f56155024337d1755721798de44789a0687d410d68759b9
Tx public key: 6f86c1f5ef60f175e0a64b60dfc9bb31d7f5f9e69cc71eccfc248429c010f2ae
Timestamp: 1694789846 Timestamp [UCT]: 2023-09-15 14:57:26 Age [y:d:h:m:s]: 01:167:03:38:59
Block: 848739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380522 RingCT/type: yes/0
Extra: 016f86c1f5ef60f175e0a64b60dfc9bb31d7f5f9e69cc71eccfc248429c010f2ae021100000003faf35c9c000000000000000000

1 output(s) for total of 0.945747982000 dcy

stealth address amount amount idx
00: 276bf016042f65d947541738e9784312246615040e5da75ef0cf6758ab016250 0.945747982000 1302363 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": 848749, "vin": [ { "gen": { "height": 848739 } } ], "vout": [ { "amount": 945747982, "target": { "key": "276bf016042f65d947541738e9784312246615040e5da75ef0cf6758ab016250" } } ], "extra": [ 1, 111, 134, 193, 245, 239, 96, 241, 117, 224, 166, 75, 96, 223, 201, 187, 49, 215, 245, 249, 230, 156, 199, 30, 204, 252, 36, 132, 41, 192, 16, 242, 174, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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