Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0227358f8727b927123b2f27045cd40cef136df61533d8b94248db775216ef

Tx prefix hash: fce8f5c9cf2f237b925c26389098520c9be67a71be9761ad5ec00519e50e2a95
Tx public key: 1223b4e05d0b4fd0c5f5a9c2e59432ab98e0ce56e2f65cb8acd54af6147f9ca9
Timestamp: 1580479990 Timestamp [UCT]: 2020-01-31 14:13:10 Age [y:d:h:m:s]: 05:003:07:39:06
Block: 55797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154256 RingCT/type: yes/0
Extra: 011223b4e05d0b4fd0c5f5a9c2e59432ab98e0ce56e2f65cb8acd54af6147f9ca9021100000003ff58ae94000000000000000000

1 output(s) for total of 400.979528702000 dcy

stealth address amount amount idx
00: 0627f3f68dbc8c498b0c525582b59b7565cf11867255350bb8b30c1ebf9b86a1 400.979528702000 102956 of 0

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": 55807, "vin": [ { "gen": { "height": 55797 } } ], "vout": [ { "amount": 400979528702, "target": { "key": "0627f3f68dbc8c498b0c525582b59b7565cf11867255350bb8b30c1ebf9b86a1" } } ], "extra": [ 1, 18, 35, 180, 224, 93, 11, 79, 208, 197, 245, 169, 194, 229, 148, 50, 171, 152, 224, 206, 86, 226, 246, 92, 184, 172, 213, 74, 246, 20, 127, 156, 169, 2, 17, 0, 0, 0, 3, 255, 88, 174, 148, 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