Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff8841db06cd8221fd4a5551a457373aba5e75f310f7c60df86dc162585e0e07

Tx prefix hash: 766a2d7d24adb27bda7eadab47e2e6b140dda180cc9797cb442af1a1cefe5380
Tx public key: d10967c502609b5a9ed8c3a482aea33bfe9cda6f5dba3446053a7c552ecaf623
Timestamp: 1706655896 Timestamp [UCT]: 2024-01-30 23:04:56 Age [y:d:h:m:s]: 01:292:13:27:24
Block: 946905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467903 RingCT/type: yes/0
Extra: 01d10967c502609b5a9ed8c3a482aea33bfe9cda6f5dba3446053a7c552ecaf62302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9e8b25f13ef7823bc32efa9674fc338b9032a8d163238edc0850cfefc56ed4 0.600000000000 1405249 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": 946915, "vin": [ { "gen": { "height": 946905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9e8b25f13ef7823bc32efa9674fc338b9032a8d163238edc0850cfefc56ed4" } } ], "extra": [ 1, 209, 9, 103, 197, 2, 96, 155, 90, 158, 216, 195, 164, 130, 174, 163, 59, 254, 156, 218, 111, 93, 186, 52, 70, 5, 58, 124, 85, 46, 202, 246, 35, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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