Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fe98d0f52e790084ba4405bea95448b7a0987f72aa2ab78762816e2dda9e0f

Tx prefix hash: 3fb1f2b596a56f61ffd55e51f7bc9800c05d005ebdcf85c158d02a701f82f7ef
Tx public key: dce446fc6a010ad9959e2b42ee749e7aa5d819aafcc21be90c43a963b0659bf3
Timestamp: 1750159432 Timestamp [UCT]: 2025-06-17 11:23:52 Age [y:d:h:m:s]: 00:149:20:15:51
Block: 1306925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104884 RingCT/type: yes/0
Extra: 01dce446fc6a010ad9959e2b42ee749e7aa5d819aafcc21be90c43a963b0659bf3021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f318550d1ea4c72a17faae03e3be77a7d3d88ad20491be82844f22617a482529 0.600000000000 1794534 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": 1306935, "vin": [ { "gen": { "height": 1306925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f318550d1ea4c72a17faae03e3be77a7d3d88ad20491be82844f22617a482529" } } ], "extra": [ 1, 220, 228, 70, 252, 106, 1, 10, 217, 149, 158, 43, 66, 238, 116, 158, 122, 165, 216, 25, 170, 252, 194, 27, 233, 12, 67, 169, 99, 176, 101, 155, 243, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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