Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979e1d6b744b4edf5f1a31da93da5ba735a39655763172cf231d0b9597a4311b

Tx prefix hash: b77ae8e1f42f6365753513d0e1e01e8c3c5ea0219f496a46c2be6367189d3312
Tx public key: 69f0973c55ef9f45bcd90c0045e53b395d284df4c6521d37e5c8d4f091c92e79
Timestamp: 1695928627 Timestamp [UCT]: 2023-09-28 19:17:07 Age [y:d:h:m:s]: 02:037:13:36:36
Block: 858200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546480 RingCT/type: yes/0
Extra: 0169f0973c55ef9f45bcd90c0045e53b395d284df4c6521d37e5c8d4f091c92e790211000000084b8f5122000000000000000000

1 output(s) for total of 0.879887583000 dcy

stealth address amount amount idx
00: a2069c8cdad3bc2c679d7d8f509c270ae29b295f85620e41c3016719f83d39ee 0.879887583000 1312366 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": 858210, "vin": [ { "gen": { "height": 858200 } } ], "vout": [ { "amount": 879887583, "target": { "key": "a2069c8cdad3bc2c679d7d8f509c270ae29b295f85620e41c3016719f83d39ee" } } ], "extra": [ 1, 105, 240, 151, 60, 85, 239, 159, 69, 188, 217, 12, 0, 69, 229, 59, 57, 93, 40, 77, 244, 198, 82, 29, 55, 229, 200, 212, 240, 145, 201, 46, 121, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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