Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa769735822580c8c38c74ef2baf92ac3ddbab529dbaf6bd7b82f135c8cefe55

Tx prefix hash: a30dc1eef48f6a0def5e1146a3e4996ebf0b78e46a7a8f3b55adbe009725d1c4
Tx public key: f973deddc67705b87e6c017b36ac4c81322db37128e5f5db758656d10af0c377
Timestamp: 1731778197 Timestamp [UCT]: 2024-11-16 17:29:57 Age [y:d:h:m:s]: 00:188:09:04:15
Block: 1155096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134515 RingCT/type: yes/0
Extra: 01f973deddc67705b87e6c017b36ac4c81322db37128e5f5db758656d10af0c377021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bc0a50cc168e1d2b4813172e3085e48164d90070f1b8341d90e4f5ca5b153d2 0.600000000000 1640711 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": 1155106, "vin": [ { "gen": { "height": 1155096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bc0a50cc168e1d2b4813172e3085e48164d90070f1b8341d90e4f5ca5b153d2" } } ], "extra": [ 1, 249, 115, 222, 221, 198, 119, 5, 184, 126, 108, 1, 123, 54, 172, 76, 129, 50, 45, 179, 113, 40, 229, 245, 219, 117, 134, 86, 209, 10, 240, 195, 119, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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