Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431def185eaf127876f955337d1fd41da35e19d529c711f88bf1112281497d3d

Tx prefix hash: 8876b0d4321d115b06d2304748387797de6ddf62851fc4cd2e2e1202f48708a8
Tx public key: 6318dfb9ba5df916aee8e4ee77a7ad8fb77052c123814f572dbcea0e8adc0f47
Timestamp: 1745859564 Timestamp [UCT]: 2025-04-28 16:59:24 Age [y:d:h:m:s]: 00:204:00:32:15
Block: 1271432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143529 RingCT/type: yes/0
Extra: 016318dfb9ba5df916aee8e4ee77a7ad8fb77052c123814f572dbcea0e8adc0f470211000000119f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f72e3a0ed4288e23243d90c0dd63c7b4c49014e15a60ea4857d34dd2cc93819a 0.600000000000 1758693 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": 1271442, "vin": [ { "gen": { "height": 1271432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72e3a0ed4288e23243d90c0dd63c7b4c49014e15a60ea4857d34dd2cc93819a" } } ], "extra": [ 1, 99, 24, 223, 185, 186, 93, 249, 22, 174, 232, 228, 238, 119, 167, 173, 143, 183, 112, 82, 193, 35, 129, 79, 87, 45, 188, 234, 14, 138, 220, 15, 71, 2, 17, 0, 0, 0, 17, 159, 159, 230, 140, 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