Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2000af57df9e4e6b9d9e61a948a1ce4415654f78701003b0936a371b121cfc

Tx prefix hash: 6a99c70fc9220ee1c964347b57d1c240674cccbec0594cfb5e06e4c6cfaada84
Tx public key: 350625cd7b1d1befc8c88674e92b9c93ee0c2b254aaf0640cf7084ad0a74c3e8
Timestamp: 1707113992 Timestamp [UCT]: 2024-02-05 06:19:52 Age [y:d:h:m:s]: 01:022:20:57:10
Block: 950709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277380 RingCT/type: yes/0
Extra: 01350625cd7b1d1befc8c88674e92b9c93ee0c2b254aaf0640cf7084ad0a74c3e802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2271b33c2730f1d318c038734694b50987678208dc0e1924ed5527fe0b6b87bf 0.600000000000 1409371 of 15

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": 950719, "vin": [ { "gen": { "height": 950709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2271b33c2730f1d318c038734694b50987678208dc0e1924ed5527fe0b6b87bf" } } ], "extra": [ 1, 53, 6, 37, 205, 123, 29, 27, 239, 200, 200, 134, 116, 233, 43, 156, 147, 238, 12, 43, 37, 74, 175, 6, 64, 207, 112, 132, 173, 10, 116, 195, 232, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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