Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f694f494acbfd371b786256a7138ac04f48e8fd9d94b2b4388abd3c8b1e5bc8

Tx prefix hash: 898da3c9d2571113d399976d38c0e1983b04a9ffa06a21315cb1c29eef718b16
Tx public key: c3da68870d599392ba38d1e9625c32109f436735ba9e64dfa0c3e75943717941
Timestamp: 1695306650 Timestamp [UCT]: 2023-09-21 14:30:50 Age [y:d:h:m:s]: 01:197:07:21:59
Block: 853033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402082 RingCT/type: yes/0
Extra: 01c3da68870d599392ba38d1e9625c32109f436735ba9e64dfa0c3e75943717941021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.915266596000 dcy

stealth address amount amount idx
00: 447466d55024276e8e88f8ca0a2c78023bb2ad9dd4ae0b6c7adbae31c1920013 0.915266596000 1306907 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": 853043, "vin": [ { "gen": { "height": 853033 } } ], "vout": [ { "amount": 915266596, "target": { "key": "447466d55024276e8e88f8ca0a2c78023bb2ad9dd4ae0b6c7adbae31c1920013" } } ], "extra": [ 1, 195, 218, 104, 135, 13, 89, 147, 146, 186, 56, 209, 233, 98, 92, 50, 16, 159, 67, 103, 53, 186, 158, 100, 223, 160, 195, 231, 89, 67, 113, 121, 65, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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