Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e545cbe728374d63965d55e187a441bf2c8c1e8e1c673c2443c1fb85486108

Tx prefix hash: 62f2c175d6ff064222d3cbbb696ec4d4b696c02bfc294e34ec1465b2eaf910df
Tx public key: 8e948def352d74c86e558bc2e1c0c99e600deba2bc571ad813025ffa02f5a679
Timestamp: 1724450865 Timestamp [UCT]: 2024-08-23 22:07:45 Age [y:d:h:m:s]: 01:077:18:26:12
Block: 1094468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314024 RingCT/type: yes/0
Extra: 018e948def352d74c86e558bc2e1c0c99e600deba2bc571ad813025ffa02f5a679021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba0e0e0538b8e0b290d3be496c461d752954a8f7cbab60f4cfa6fa1a619c78a3 0.600000000000 1569585 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": 1094478, "vin": [ { "gen": { "height": 1094468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba0e0e0538b8e0b290d3be496c461d752954a8f7cbab60f4cfa6fa1a619c78a3" } } ], "extra": [ 1, 142, 148, 141, 239, 53, 45, 116, 200, 110, 85, 139, 194, 225, 192, 201, 158, 96, 13, 235, 162, 188, 87, 26, 216, 19, 2, 95, 250, 2, 245, 166, 121, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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