Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba5bd9888dbcbc148665ac2c91ace98dbb70fc54af73f6fd266c1f6ca545940

Tx prefix hash: 6ca67172646e4fe5e106c6811c2aaf98d97c323e9ba5f13770ac822267161c99
Tx public key: c6fce5ea96d7c79dcf0ae8ac86d008676578099f63f7b9cb59c730a100d42fb4
Timestamp: 1640216795 Timestamp [UCT]: 2021-12-22 23:46:35 Age [y:d:h:m:s]: 02:320:11:39:52
Block: 401391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 747101 RingCT/type: yes/0
Extra: 01c6fce5ea96d7c79dcf0ae8ac86d008676578099f63f7b9cb59c730a100d42fb40211000000037659c797000000000000000000

1 output(s) for total of 28.709480968000 dcy

stealth address amount amount idx
00: e26be3cc9abaa36d0838b278294de063e16259518f9ff45ad4548caad9e1f082 28.709480968000 800970 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": 401401, "vin": [ { "gen": { "height": 401391 } } ], "vout": [ { "amount": 28709480968, "target": { "key": "e26be3cc9abaa36d0838b278294de063e16259518f9ff45ad4548caad9e1f082" } } ], "extra": [ 1, 198, 252, 229, 234, 150, 215, 199, 157, 207, 10, 232, 172, 134, 208, 8, 103, 101, 120, 9, 159, 99, 247, 185, 203, 89, 199, 48, 161, 0, 212, 47, 180, 2, 17, 0, 0, 0, 3, 118, 89, 199, 151, 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