Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc299e3409f0a37f2a239edde8faa2f1a3e560dc1cd767f5a206740b8135b0c6

Tx prefix hash: 4feb21eeacebc4713c5d468c9b9720293bed91a00c3a34396100d88e9a091ed4
Tx public key: c67a4a11c4343ac2f0a00332bf15f0062b265b6b0b094559af71032bee176997
Timestamp: 1702836224 Timestamp [UCT]: 2023-12-17 18:03:44 Age [y:d:h:m:s]: 01:034:00:39:25
Block: 915265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285634 RingCT/type: yes/0
Extra: 01c67a4a11c4343ac2f0a00332bf15f0062b265b6b0b094559af71032bee176997021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 479d59feaa6336238e7a9f610a28ae13c85fa94415a05ffebbba0369a0c32084 0.600000000000 1372655 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": 915275, "vin": [ { "gen": { "height": 915265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "479d59feaa6336238e7a9f610a28ae13c85fa94415a05ffebbba0369a0c32084" } } ], "extra": [ 1, 198, 122, 74, 17, 196, 52, 58, 194, 240, 160, 3, 50, 191, 21, 240, 6, 43, 38, 91, 107, 11, 9, 69, 89, 175, 113, 3, 43, 238, 23, 105, 151, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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