Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ec2f03052af9356f37cf6d9d1af0c4dba468fd5d197303a0e0d66994f33ad3

Tx prefix hash: 75bc2c28cb51686a6d596a12cccb5b334a319d7d1a99184d8966ae7044ea548d
Tx public key: 177d35476c173096d0bd7ecec63f8b25b6b4e3a066677beefd945451c242906e
Timestamp: 1705130587 Timestamp [UCT]: 2024-01-13 07:23:07 Age [y:d:h:m:s]: 01:096:23:38:04
Block: 934256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330434 RingCT/type: yes/0
Extra: 01177d35476c173096d0bd7ecec63f8b25b6b4e3a066677beefd945451c242906e0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33eed25a4f0f600e6f619aa35824911bae56f82b18c2340ffe5f84d4af7f99b6 0.600000000000 1392246 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": 934266, "vin": [ { "gen": { "height": 934256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33eed25a4f0f600e6f619aa35824911bae56f82b18c2340ffe5f84d4af7f99b6" } } ], "extra": [ 1, 23, 125, 53, 71, 108, 23, 48, 150, 208, 189, 126, 206, 198, 63, 139, 37, 182, 180, 227, 160, 102, 103, 123, 238, 253, 148, 84, 81, 194, 66, 144, 110, 2, 17, 0, 0, 0, 9, 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