Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9074f5cd39382bc2ba8dd306fcb52b97451f25c99f73e1bd49dd445da9a0094e

Tx prefix hash: 6bce5868f6a0ebaa2a9253f9f7d89c235b3b45a8dea09c9d94e8df36e9e0821b
Tx public key: 734f3bfec96be5c5b3d8b330d52ac11fe157236777f7bb5b9bb4bc3d1169c4a0
Timestamp: 1736136564 Timestamp [UCT]: 2025-01-06 04:09:24 Age [y:d:h:m:s]: 00:154:18:06:59
Block: 1191210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110424 RingCT/type: yes/0
Extra: 01734f3bfec96be5c5b3d8b330d52ac11fe157236777f7bb5b9bb4bc3d1169c4a00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58e95bcf59a8c91b8f9bb5def0b5c70f1e8e2930651f2344b915728e50a38bf2 0.600000000000 1677733 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": 1191220, "vin": [ { "gen": { "height": 1191210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58e95bcf59a8c91b8f9bb5def0b5c70f1e8e2930651f2344b915728e50a38bf2" } } ], "extra": [ 1, 115, 79, 59, 254, 201, 107, 229, 197, 179, 216, 179, 48, 213, 42, 193, 31, 225, 87, 35, 103, 119, 247, 187, 91, 155, 180, 188, 61, 17, 105, 196, 160, 2, 17, 0, 0, 0, 1, 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