Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05bc471034c4d6276fe8675c8408f941a60e20e924abe592d4fd343a6946e2d

Tx prefix hash: 77970b72c8f2bd7f9641e58893fbcfbfcca539fb25d18f0a7f7913e86c63b0e5
Tx public key: a4d43c73961f45256ffc91e6f2fb9f17769bfd1570a39adc4e8a91cce7d62434
Timestamp: 1752922649 Timestamp [UCT]: 2025-07-19 10:57:29 Age [y:d:h:m:s]: 00:171:13:45:05
Block: 1328772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121485 RingCT/type: yes/0
Extra: 01a4d43c73961f45256ffc91e6f2fb9f17769bfd1570a39adc4e8a91cce7d62434021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 736f3035aca4155896d8690573b74bf8ab3da916ee921a8a7d9d886847d6dfc5 0.600000000000 1816543 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": 1328782, "vin": [ { "gen": { "height": 1328772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "736f3035aca4155896d8690573b74bf8ab3da916ee921a8a7d9d886847d6dfc5" } } ], "extra": [ 1, 164, 212, 60, 115, 150, 31, 69, 37, 111, 252, 145, 230, 242, 251, 159, 23, 118, 155, 253, 21, 112, 163, 154, 220, 78, 138, 145, 204, 231, 214, 36, 52, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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