Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ba4449b6077a868cf2d30c16febb0a981565867e99486b54f928ff798d306a

Tx prefix hash: ba2be62e6331f5d8a9ff7c22606a960578d916b649741ed9dd92e2699b8faa4b
Tx public key: a4825ceeef2ae3ac3fc44338ba7ae7ef67c0f896a8604306a9a9a76210768125
Timestamp: 1735925731 Timestamp [UCT]: 2025-01-03 17:35:31 Age [y:d:h:m:s]: 00:354:11:07:52
Block: 1189464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250886 RingCT/type: yes/0
Extra: 01a4825ceeef2ae3ac3fc44338ba7ae7ef67c0f896a8604306a9a9a762107681250211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cfd7f54d52e691c54df506d3da8fbdb031bada86112be6b4f03ea1cfee766d3 0.600000000000 1675973 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": 1189474, "vin": [ { "gen": { "height": 1189464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cfd7f54d52e691c54df506d3da8fbdb031bada86112be6b4f03ea1cfee766d3" } } ], "extra": [ 1, 164, 130, 92, 238, 239, 42, 227, 172, 63, 196, 67, 56, 186, 122, 231, 239, 103, 192, 248, 150, 168, 96, 67, 6, 169, 169, 167, 98, 16, 118, 129, 37, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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