Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d2798b5114626d88f8d75a2aee5f5e104ece886ba82e0bbfb0d075a3adc6f84

Tx prefix hash: f332aeeb99904ba9e9de1d96ec3841b1602e14fe66a4df9d68157330ef73b658
Tx public key: 519b679e1d18e8b995a208e5d75c9774283d08d2536f672c19ce8c053762c907
Timestamp: 1744106500 Timestamp [UCT]: 2025-04-08 10:01:40 Age [y:d:h:m:s]: 00:216:13:20:58
Block: 1256900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152503 RingCT/type: yes/0
Extra: 01519b679e1d18e8b995a208e5d75c9774283d08d2536f672c19ce8c053762c907021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5febca3477b1e8e628502a407ebf5a3ba44cc87bbd248d12d1a01c72a9d8fca 0.600000000000 1744017 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": 1256910, "vin": [ { "gen": { "height": 1256900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5febca3477b1e8e628502a407ebf5a3ba44cc87bbd248d12d1a01c72a9d8fca" } } ], "extra": [ 1, 81, 155, 103, 158, 29, 24, 232, 185, 149, 162, 8, 229, 215, 92, 151, 116, 40, 61, 8, 210, 83, 111, 103, 44, 25, 206, 140, 5, 55, 98, 201, 7, 2, 17, 0, 0, 0, 3, 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