Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725bbfd7852dc88306d6edd2a2624494c7923cdcd9ec87a7e0054c01ced529b5

Tx prefix hash: 909f7241fc0788e9593f59bf1a038f610e28fca2e52b20968c0aa2c10c837e77
Tx public key: f48bbf77fbd12e63e93f886f4723f7f4dda0a15a5040bfebcc9f02491e1d6412
Timestamp: 1746018502 Timestamp [UCT]: 2025-04-30 13:08:22 Age [y:d:h:m:s]: 00:205:04:11:24
Block: 1272738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144352 RingCT/type: yes/0
Extra: 01f48bbf77fbd12e63e93f886f4723f7f4dda0a15a5040bfebcc9f02491e1d641202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fe099d233c1a841dbf011d5e2c532047aa7108fa0a871dde933b18d43936bef 0.600000000000 1760013 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": 1272748, "vin": [ { "gen": { "height": 1272738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fe099d233c1a841dbf011d5e2c532047aa7108fa0a871dde933b18d43936bef" } } ], "extra": [ 1, 244, 139, 191, 119, 251, 209, 46, 99, 233, 63, 136, 111, 71, 35, 247, 244, 221, 160, 161, 90, 80, 64, 191, 235, 204, 159, 2, 73, 30, 29, 100, 18, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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