Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62022e0ba439a4d3b1f2999af636b8e662c68a17fe801a3531bf73d491a031dd

Tx prefix hash: 7146873d00ac63ff61e8102dc927ce445ef7f2baaa19c1729ac7a1238d4a18bd
Tx public key: 868c36d71c08f4d1d8eacebe47400e66d60743048dcf98bf56b9bd548f4b626c
Timestamp: 1727840452 Timestamp [UCT]: 2024-10-02 03:40:52 Age [y:d:h:m:s]: 01:037:08:46:16
Block: 1122563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285077 RingCT/type: yes/0
Extra: 01868c36d71c08f4d1d8eacebe47400e66d60743048dcf98bf56b9bd548f4b626c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29ad82b6fcc1eb98c5e1776f94ce56ef79e288d4dfb059779ea00caf61b9e2f5 0.600000000000 1605032 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": 1122573, "vin": [ { "gen": { "height": 1122563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29ad82b6fcc1eb98c5e1776f94ce56ef79e288d4dfb059779ea00caf61b9e2f5" } } ], "extra": [ 1, 134, 140, 54, 215, 28, 8, 244, 209, 216, 234, 206, 190, 71, 64, 14, 102, 214, 7, 67, 4, 141, 207, 152, 191, 86, 185, 189, 84, 143, 75, 98, 108, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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