Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0111d5843101d504b4ad07368ed8f2d941587c062196a3200269a9e9096ec562

Tx prefix hash: bba22f1d19b691cee0941e3b5c329d2e767b8f1fd0e497b9141c8624c0fc237d
Tx public key: af6fdfd49225d7e9c226bb3964bbee0057899d470ad61f90c354ab4f5def2b4a
Timestamp: 1656985594 Timestamp [UCT]: 2022-07-05 01:46:34 Age [y:d:h:m:s]: 02:182:14:12:10
Block: 536832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651855 RingCT/type: yes/0
Extra: 01af6fdfd49225d7e9c226bb3964bbee0057899d470ad61f90c354ab4f5def2b4a02110000000433af99f4000000000000000000

1 output(s) for total of 10.215341412000 dcy

stealth address amount amount idx
00: 312354f2c028ba35d68ef36b13422d9d897f2e10df9a47bb8b0f2a3233dd1cf0 10.215341412000 966639 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": 536842, "vin": [ { "gen": { "height": 536832 } } ], "vout": [ { "amount": 10215341412, "target": { "key": "312354f2c028ba35d68ef36b13422d9d897f2e10df9a47bb8b0f2a3233dd1cf0" } } ], "extra": [ 1, 175, 111, 223, 212, 146, 37, 215, 233, 194, 38, 187, 57, 100, 187, 238, 0, 87, 137, 157, 71, 10, 214, 31, 144, 195, 84, 171, 79, 93, 239, 43, 74, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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