Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a448f7a13355da4db2dec843a6ee6ad516b4050dfb4bef8c52898d24fa39e19f

Tx prefix hash: 734dd719825607e8a7a9c00d462ab9ff9acdab9fed9a43c917d5c3f6bf3d895b
Tx public key: 9a65ee68b4870d58e2cd9d998c5c3276a528a4b887fb553828de1b364fb82177
Timestamp: 1681250866 Timestamp [UCT]: 2023-04-11 22:07:46 Age [y:d:h:m:s]: 01:279:22:47:49
Block: 736544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461585 RingCT/type: yes/0
Extra: 019a65ee68b4870d58e2cd9d998c5c3276a528a4b887fb553828de1b364fb821770211000000015029cbac000000000000000000

1 output(s) for total of 2.225995064000 dcy

stealth address amount amount idx
00: 569e59dedbeb3400495be37dbae43d6ae7da4011137612e7f008e93ee4026f8f 2.225995064000 1182993 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": 736554, "vin": [ { "gen": { "height": 736544 } } ], "vout": [ { "amount": 2225995064, "target": { "key": "569e59dedbeb3400495be37dbae43d6ae7da4011137612e7f008e93ee4026f8f" } } ], "extra": [ 1, 154, 101, 238, 104, 180, 135, 13, 88, 226, 205, 157, 153, 140, 92, 50, 118, 165, 40, 164, 184, 135, 251, 85, 56, 40, 222, 27, 54, 79, 184, 33, 119, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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