Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46444f4753d72580a7e81363334be57f9950f81056807256624d77d6b72095ab

Tx prefix hash: 52da1accbd1aab8a132327081f814559563021095f8d1d0d018680ace8687a48
Tx public key: f0ffd8f943eb8bd3248500034d5f65ad6b5b0b1363d7cba66d2e636222da57da
Timestamp: 1685322782 Timestamp [UCT]: 2023-05-29 01:13:02 Age [y:d:h:m:s]: 02:160:14:48:04
Block: 770310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634578 RingCT/type: yes/0
Extra: 01f0ffd8f943eb8bd3248500034d5f65ad6b5b0b1363d7cba66d2e636222da57da02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.720455217000 dcy

stealth address amount amount idx
00: c6c840a6d2eea1be0b0069fdce88b7cbf8a8e48a10fcb8b44590d1e7959cba60 1.720455217000 1219611 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": 770320, "vin": [ { "gen": { "height": 770310 } } ], "vout": [ { "amount": 1720455217, "target": { "key": "c6c840a6d2eea1be0b0069fdce88b7cbf8a8e48a10fcb8b44590d1e7959cba60" } } ], "extra": [ 1, 240, 255, 216, 249, 67, 235, 139, 211, 36, 133, 0, 3, 77, 95, 101, 173, 107, 91, 11, 19, 99, 215, 203, 166, 109, 46, 99, 98, 34, 218, 87, 218, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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