Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc39a136a6400d661d83c374158475df55d6a4baa984130f98db4fba0c916e9

Tx prefix hash: 0fa75efa927d363f59e8b57bc918d339815b30c028fa2f73221f271259ff9727
Tx public key: 1f327623992ce0c92b536ae056a247c650ae102d21c4c16545e28f414666d515
Timestamp: 1669343419 Timestamp [UCT]: 2022-11-25 02:30:19 Age [y:d:h:m:s]: 02:131:04:42:54
Block: 638487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615483 RingCT/type: yes/0
Extra: 011f327623992ce0c92b536ae056a247c650ae102d21c4c16545e28f414666d51502110000000383600029000000000000000000

1 output(s) for total of 4.703569048000 dcy

stealth address amount amount idx
00: 1cfc59f50e6ffc2750e45ab25c43ab29486a69aa4b4a4bc7f2c8755a10c88dd3 4.703569048000 1078102 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": 638497, "vin": [ { "gen": { "height": 638487 } } ], "vout": [ { "amount": 4703569048, "target": { "key": "1cfc59f50e6ffc2750e45ab25c43ab29486a69aa4b4a4bc7f2c8755a10c88dd3" } } ], "extra": [ 1, 31, 50, 118, 35, 153, 44, 224, 201, 43, 83, 106, 224, 86, 162, 71, 198, 80, 174, 16, 45, 33, 196, 193, 101, 69, 226, 143, 65, 70, 102, 213, 21, 2, 17, 0, 0, 0, 3, 131, 96, 0, 41, 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