Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92c79ee9052afa0ecf8f3b59b09df93fdce0a4ae4635d4466662c1c2d32ddf71

Tx prefix hash: 544b0bb6dff161d9e8aa33706776403495285d7b3b6f0d67dcacdbaf188ed1d6
Tx public key: b4e45b7f5ef6f1ec6e740c078a67fbe5ef76adc1313c9f462c82b2876be15cd2
Timestamp: 1730432647 Timestamp [UCT]: 2024-11-01 03:44:07 Age [y:d:h:m:s]: 01:031:23:16:31
Block: 1143960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281309 RingCT/type: yes/0
Extra: 01b4e45b7f5ef6f1ec6e740c078a67fbe5ef76adc1313c9f462c82b2876be15cd2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c20c296b360d3c59b2fd6dfe7528a1f71eaa06ffa9a18d697caae0d7cb17e316 0.600000000000 1628009 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": 1143970, "vin": [ { "gen": { "height": 1143960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c20c296b360d3c59b2fd6dfe7528a1f71eaa06ffa9a18d697caae0d7cb17e316" } } ], "extra": [ 1, 180, 228, 91, 127, 94, 246, 241, 236, 110, 116, 12, 7, 138, 103, 251, 229, 239, 118, 173, 193, 49, 60, 159, 70, 44, 130, 178, 135, 107, 225, 92, 210, 2, 17, 0, 0, 0, 4, 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