Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19128b12ff062e1f6c3c697e5c365f216c5b20e024736fde0165c076fda3f321

Tx prefix hash: efa910e264aa392d6aa994adfb384c0301b6dc883272bf88fed92083602c022d
Tx public key: 77a41f15dc54e5f003e1a4ae217123d857ad6501d00c2282103c7cbc620c7436
Timestamp: 1713853717 Timestamp [UCT]: 2024-04-23 06:28:37 Age [y:d:h:m:s]: 00:308:01:06:38
Block: 1006604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220177 RingCT/type: yes/0
Extra: 0177a41f15dc54e5f003e1a4ae217123d857ad6501d00c2282103c7cbc620c74360211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf4cde6134c18dc2b17764f36a0a50425c011952870ff9b5538c32cf98fd702 0.600000000000 1467682 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": 1006614, "vin": [ { "gen": { "height": 1006604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf4cde6134c18dc2b17764f36a0a50425c011952870ff9b5538c32cf98fd702" } } ], "extra": [ 1, 119, 164, 31, 21, 220, 84, 229, 240, 3, 225, 164, 174, 33, 113, 35, 216, 87, 173, 101, 1, 208, 12, 34, 130, 16, 60, 124, 188, 98, 12, 116, 54, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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