Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ec2a64993725a91eea9e049319c6fc5e039a234b6c68649313e0fe2b3fe1ee

Tx prefix hash: 3939fd6042fe63eaf9b6010af39f41578e103df9ab60ac55436e39cf1b098646
Tx public key: 0c3f309a5d5d783fd17518ecdac1c34476166b789872f8ffec13dafa067c2a15
Timestamp: 1682784230 Timestamp [UCT]: 2023-04-29 16:03:50 Age [y:d:h:m:s]: 01:301:12:24:37
Block: 749270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476702 RingCT/type: yes/0
Extra: 010c3f309a5d5d783fd17518ecdac1c34476166b789872f8ffec13dafa067c2a1502110000000175e3f0e9000000000000000000

1 output(s) for total of 2.020029247000 dcy

stealth address amount amount idx
00: 619f286dbec35b59035dd11e55b562b6f92475a40a666ef934ac4f4971ce0b28 2.020029247000 1197217 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": 749280, "vin": [ { "gen": { "height": 749270 } } ], "vout": [ { "amount": 2020029247, "target": { "key": "619f286dbec35b59035dd11e55b562b6f92475a40a666ef934ac4f4971ce0b28" } } ], "extra": [ 1, 12, 63, 48, 154, 93, 93, 120, 63, 209, 117, 24, 236, 218, 193, 195, 68, 118, 22, 107, 120, 152, 114, 248, 255, 236, 19, 218, 250, 6, 124, 42, 21, 2, 17, 0, 0, 0, 1, 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