Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e86347068b52f50d611d11bdd35c3824b3c51526367f64db2738d78fbb7e766

Tx prefix hash: fb364e32ebb071eda9d83ae1ccac9b129f58d3cfc6013adc2e25a08d8e5b280e
Tx public key: 1b5582239d6c2ffca457531d0742776b1d3600e1bbbbd0ffd2d8e229177c8620
Timestamp: 1718217905 Timestamp [UCT]: 2024-06-12 18:45:05 Age [y:d:h:m:s]: 00:207:13:25:07
Block: 1042785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148548 RingCT/type: yes/0
Extra: 011b5582239d6c2ffca457531d0742776b1d3600e1bbbbd0ffd2d8e229177c86200211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49c53c5c8fa195f0869a7bdbe4b908a2c3e133c08334c7291dd33d2d0111b3dd 0.600000000000 1511782 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": 1042795, "vin": [ { "gen": { "height": 1042785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49c53c5c8fa195f0869a7bdbe4b908a2c3e133c08334c7291dd33d2d0111b3dd" } } ], "extra": [ 1, 27, 85, 130, 35, 157, 108, 47, 252, 164, 87, 83, 29, 7, 66, 119, 107, 29, 54, 0, 225, 187, 187, 208, 255, 210, 216, 226, 41, 23, 124, 134, 32, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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