Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c8b20076f56dc6ba02b6e59289623fa87dbe18bf6835afd1bacb7d99f2ff4c

Tx prefix hash: f8e995359dc05c4098006c3b3e6083c127fb81b2c7c604568d0635266e3a98a5
Tx public key: 8c9cc7c9e16117b83dd541da7f62aa24120468e0d007ac223f7e8209d464136a
Timestamp: 1730150995 Timestamp [UCT]: 2024-10-28 21:29:55 Age [y:d:h:m:s]: 00:158:04:11:19
Block: 1141647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112867 RingCT/type: yes/0
Extra: 018c9cc7c9e16117b83dd541da7f62aa24120468e0d007ac223f7e8209d464136a0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6247e219ea34aa62109fcfa14ffb347fbef9018ef3d44d01e61503b1c9b2e1a9 0.600000000000 1625458 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": 1141657, "vin": [ { "gen": { "height": 1141647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6247e219ea34aa62109fcfa14ffb347fbef9018ef3d44d01e61503b1c9b2e1a9" } } ], "extra": [ 1, 140, 156, 199, 201, 225, 97, 23, 184, 61, 213, 65, 218, 127, 98, 170, 36, 18, 4, 104, 224, 208, 7, 172, 34, 63, 126, 130, 9, 212, 100, 19, 106, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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