Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b06fc0d154eae40fc2ca03acb59c8b4873ae70d727bac12b22ada0a2d355961

Tx prefix hash: a3b5a1d516d5785a2b37f4bdd6f0cce265f694837524dac482c74d1d6b8bc499
Tx public key: 6e253ae85a0bc3822432bec7293d31630c0a3672caa761c72f7a1f81b43b9073
Timestamp: 1736417707 Timestamp [UCT]: 2025-01-09 10:15:07 Age [y:d:h:m:s]: 00:341:11:08:36
Block: 1193523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241590 RingCT/type: yes/0
Extra: 016e253ae85a0bc3822432bec7293d31630c0a3672caa761c72f7a1f81b43b90730211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 609f584a2507d3d8d05c8789e050f23fc058c0ae8a6168f1a7a85ef92116b60e 0.600000000000 1680084 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": 1193533, "vin": [ { "gen": { "height": 1193523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "609f584a2507d3d8d05c8789e050f23fc058c0ae8a6168f1a7a85ef92116b60e" } } ], "extra": [ 1, 110, 37, 58, 232, 90, 11, 195, 130, 36, 50, 190, 199, 41, 61, 49, 99, 12, 10, 54, 114, 202, 167, 97, 199, 47, 122, 31, 129, 180, 59, 144, 115, 2, 17, 0, 0, 0, 7, 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