Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f307c3eaa51bf0e4dca061485b62fbae3dd44e65ed42125a41d091fc2e6719a8

Tx prefix hash: 412b846682d1c3faad151a678246e8eb1737c8aad8038b1a4b2236a01e5b53ac
Tx public key: 42c282417de5e2e1fee620dec7d8640951dab9cd7e075ebb9b03a4464143328c
Timestamp: 1755896318 Timestamp [UCT]: 2025-08-22 20:58:38 Age [y:d:h:m:s]: 00:038:22:16:41
Block: 1352229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27685 RingCT/type: yes/0
Extra: 0142c282417de5e2e1fee620dec7d8640951dab9cd7e075ebb9b03a4464143328c0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2cfe8bc26ff71170c4c743c6d9a40c502e97fe982cb95bbb3dfb6ded4b3d428 0.600000000000 1840192 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": 1352239, "vin": [ { "gen": { "height": 1352229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2cfe8bc26ff71170c4c743c6d9a40c502e97fe982cb95bbb3dfb6ded4b3d428" } } ], "extra": [ 1, 66, 194, 130, 65, 125, 229, 226, 225, 254, 230, 32, 222, 199, 216, 100, 9, 81, 218, 185, 205, 126, 7, 94, 187, 155, 3, 164, 70, 65, 67, 50, 140, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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