Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890faad9c89dd7dbb018b59e35df85b47d7f7f1f45ac7d5ccef6ff144575de37

Tx prefix hash: 181705f492ab29b5feb32705fe8683bd7c7f7b6481558a343891e4f5a6bd5e23
Tx public key: 295fd52c7110356f4e2451f54657242578c05cec0e8a33a061a326e008b240f9
Timestamp: 1733376953 Timestamp [UCT]: 2024-12-05 05:35:53 Age [y:d:h:m:s]: 00:130:09:38:28
Block: 1168354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93008 RingCT/type: yes/0
Extra: 01295fd52c7110356f4e2451f54657242578c05cec0e8a33a061a326e008b240f90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6424f8b49bd71f0038c8b4ea628b27fc6f1a2c919603e9e20ac626d1990b2338 0.600000000000 1654063 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": 1168364, "vin": [ { "gen": { "height": 1168354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6424f8b49bd71f0038c8b4ea628b27fc6f1a2c919603e9e20ac626d1990b2338" } } ], "extra": [ 1, 41, 95, 213, 44, 113, 16, 53, 111, 78, 36, 81, 245, 70, 87, 36, 37, 120, 192, 92, 236, 14, 138, 51, 160, 97, 163, 38, 224, 8, 178, 64, 249, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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