Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf7e741c412112405ae0c6ff9d5abc2dd7915d5a2b193612bfc9864b9aa52af1

Tx prefix hash: 8afbc1aecadd09b1461c9b6f4715ddc8d64a312480cc17ee00a13dd97e135baa
Tx public key: d288c411b2ec5889d94afd1e3196673980b4e6ae1819d29800dc558bd902d3cf
Timestamp: 1744498698 Timestamp [UCT]: 2025-04-12 22:58:18 Age [y:d:h:m:s]: 00:029:13:04:25
Block: 1260151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21142 RingCT/type: yes/0
Extra: 01d288c411b2ec5889d94afd1e3196673980b4e6ae1819d29800dc558bd902d3cf021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a5ad215b9cb6b106d6c6f569f3182be66194da12bfdc08f20e34f1476652ae0 0.600000000000 1747302 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": 1260161, "vin": [ { "gen": { "height": 1260151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a5ad215b9cb6b106d6c6f569f3182be66194da12bfdc08f20e34f1476652ae0" } } ], "extra": [ 1, 210, 136, 196, 17, 178, 236, 88, 137, 217, 74, 253, 30, 49, 150, 103, 57, 128, 180, 230, 174, 24, 25, 210, 152, 0, 220, 85, 139, 217, 2, 211, 207, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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