Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635be1db5d5b5ffc985094d1d5915ed92e2d36dc66cebe6d24a9526a3dffe8d1

Tx prefix hash: 2ce6125ec7f06bb8d8ee20b466f64059c3e493acd05c337a326e73b1d1f2b29b
Tx public key: 21c4b7c0f92d470ecaf04f216492f56dc29e3e0a49e7ad5423555a59196d4e9d
Timestamp: 1675241414 Timestamp [UCT]: 2023-02-01 08:50:14 Age [y:d:h:m:s]: 02:117:15:58:34
Block: 687356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605774 RingCT/type: yes/0
Extra: 0121c4b7c0f92d470ecaf04f216492f56dc29e3e0a49e7ad5423555a59196d4e9d0211000000017e406890000000000000000000

1 output(s) for total of 3.239695322000 dcy

stealth address amount amount idx
00: a4c017fe4a182161682bae084148ad0c1a97d42d2efdcb56c2520df500566f01 3.239695322000 1129916 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": 687366, "vin": [ { "gen": { "height": 687356 } } ], "vout": [ { "amount": 3239695322, "target": { "key": "a4c017fe4a182161682bae084148ad0c1a97d42d2efdcb56c2520df500566f01" } } ], "extra": [ 1, 33, 196, 183, 192, 249, 45, 71, 14, 202, 240, 79, 33, 100, 146, 245, 109, 194, 158, 62, 10, 73, 231, 173, 84, 35, 85, 90, 89, 25, 109, 78, 157, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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