Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d8b95cf33ad2d5202608b5cc74c765cc5c1262833e4d0059de832cb4f65acd

Tx prefix hash: 7ec31166eb960d686a4cc32ca981d61d986f5ed13a6652cfd1f00f63fcbfa338
Tx public key: 836503ad4b49918eb07b1a2e090f117dcbfea4d486d00a1a71c6fb60cdbe2f7a
Timestamp: 1704877266 Timestamp [UCT]: 2024-01-10 09:01:06 Age [y:d:h:m:s]: 01:109:02:18:05
Block: 932167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339096 RingCT/type: yes/0
Extra: 01836503ad4b49918eb07b1a2e090f117dcbfea4d486d00a1a71c6fb60cdbe2f7a0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a5ddd75785e1beadd3f7d8d04ce2459417fc2429ffd899300f50c15462e730 0.600000000000 1390091 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": 932177, "vin": [ { "gen": { "height": 932167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a5ddd75785e1beadd3f7d8d04ce2459417fc2429ffd899300f50c15462e730" } } ], "extra": [ 1, 131, 101, 3, 173, 75, 73, 145, 142, 176, 123, 26, 46, 9, 15, 17, 125, 203, 254, 164, 212, 134, 208, 10, 26, 113, 198, 251, 96, 205, 190, 47, 122, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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